| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Allow --noflush with dmsetup status and wait (for thin target 1.3.0 /
ioctl 4.23.0).
|
| |
|
|
|
| |
It will be user for cryptsetup to ensure buffers are properly
wiped when sending sensitive data (key).
|
| | |
|
| |
|
|
| |
Add dm_task_set_newuuid to set uuid of mapped device post-creation. (pjones)
|
| |
|
|
|
|
|
|
| |
A kernel patch is on its way for 2.6.35 adding support for dm-mod module
autoload. Udev v155 and higher is able to read static node information given
in modules.devname (extracted by depmod before) and will create such nodes
at its start. The first access to such node will load the module automatically
(directly in kernel) before the actual read/write operation is processed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We need to know whether we should wait for any uevent or not when
using udev_sync. A kernel patch was posted recently that changed the
way uevents are sent on dm device resume - it is sent only if the
device has been suspended before. There's also a new DM_UEVENT_GENERATED_FLAG
in the ioctl to notify userspace whether the event was generated.
If the uevent was not generated (e.g. the situation where the device is
*not* suspended and we call a resume), we just call dm_udev_complete
explicitly from within libdevmapper itself to prevent infinite waiting
while trying to synchronise with udev processing.
|
| |
|
|
|
| |
Currently this data is invisible to userspace.
Requires dm >= 4.16 (likely to be in linux 2.6.33).
|
| |
|
|
| |
Update dm-ioctl.h comments.
|
| |
|
