summaryrefslogtreecommitdiff
path: root/WHATS_NEW_DM
diff options
context:
space:
mode:
authorPeter Rajnoha <prajnoha@redhat.com>2014-09-12 12:49:37 +0200
committerPeter Rajnoha <prajnoha@redhat.com>2014-09-12 12:49:37 +0200
commit3880ca5ecad1761bd13a190c58f8f85fdd7cd0e1 (patch)
treec48772bc2b9e62872c0a18d3df5bdb6e496649b0 /WHATS_NEW_DM
parentf0cafc92812e285e5120241da04b5d119b27060b (diff)
downloadlvm2-3880ca5ecad1761bd13a190c58f8f85fdd7cd0e1.tar.gz
libdm: use dm-mod autoloading during dm_is_dm_major call if needed
For dm_is_dm_major to determine whether the major number given as an argument belongs to a DM device, libdm code needs to know what the actual DM major is to do the comparison. It may happen that the dm-mod module is not loaded during this call and so for the completness let's try our best before we start giving various errors - we can still make use of dm-mod autoloading, though only since kernels 2.6.36 where this feature was introduced.
Diffstat (limited to 'WHATS_NEW_DM')
-rw-r--r--WHATS_NEW_DM1
1 files changed, 1 insertions, 0 deletions
diff --git a/WHATS_NEW_DM b/WHATS_NEW_DM
index 4effe09e0..1374934dd 100644
--- a/WHATS_NEW_DM
+++ b/WHATS_NEW_DM
@@ -1,5 +1,6 @@
Version 1.02.91 -
====================================
+ Use dm-mod autoloading during dm_is_dm_major call if needed (kernels>=2.6.36).
Version 1.02.90 - 1st September 2014
====================================