mirror of
git://sourceware.org/git/lvm2.git
synced 2025-03-19 22:50:38 +03:00
14ad41a065
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.
This tree contains the LVM2 and device-mapper tools and libraries. For more information about LVM2 read the changelog in the WHATS_NEW file. Installation instructions are in INSTALL. There is no warranty - see COPYING and COPYING.LIB. Tarballs are available from: ftp://sources.redhat.com/pub/lvm2/ To access the CVS tree use: cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm2 login CVS password: cvs cvs -d :pserver:cvs@sources.redhat.com:/cvs/lvm2 co LVM2 Mailing list for general discussion related to LVM2: linux-lvm@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/linux-lvm Mailing list for LVM2 development, patches and commits: lvm-devel@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/linux-lvm Mailing list for device-mapper development, including kernel patches and multipath-tools: dm-devel@redhat.com Subscribe from https://www.redhat.com/mailman/listinfo/dm-devel