Failure to auto-load dm-mod kernel module
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
Expired
|
High
|
Unassigned |
Bug Description
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.
Alternatively, one could perhaps patch the libdevmapper library itself to automatically execute the modprobe whenever a client application needs access to /dev/mapper/
A third possibility might be some form of udev rule triggered on access to /dev/mapper/
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.
Changed in devmapper: | |
assignee: | ubuntu-kernel-team → nobody |
Changed in devmapper: | |
status: | Confirmed → Triaged |
Assigning to the kernel team; looks like this bug is fairly well described, and has several likely duplicates.