Public bug reported:
The libdevmapper package (1.02.08 in ubuntu-7.04-beta) does not auto-
load the kernel dm-mod module either at system bootup, or when first
used by a client application (e.g. cryptsetup, cryptmount). This means
that those client applications will typically fail unless the user
executes "sudo modprobe dm-mod" (or equivalents) beforehand. Clearly, it
is far better that a common solution be implemented within the
libdevmapper package rather than separately within each client of the
libdevmapper library.
In the debian libdevmapper package, there is an /etc/init.d/libdevmapper script
which executes "modprobe dm-mod" at system bootup, and this seems to work
perfectly as a solution (provided the kernel doesn't auto un-load the module
later - which I've not noticed on kernels up to 2.6.18).
Alternatively, one could perhaps patch the libdevmapper library itself to
automatically execute the modprobe whenever a client application needs access
to /dev/mapper/control.
A third possibility might be some form of udev rule triggered on access to
/dev/mapper/control.
Without some form of fix to libdevmapper, usage of applications such as
cryptmount, cryptsetup, dmsetup is always likely to be compromised.
Fixing this is likely to fix bugs 64625, 93568, 91405, 104452.
** Affects: devmapper (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Failure to auto-load dm-mod kernel module
https://bugs.launchpad.net/bugs/106696
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
