From mboxrd@z Thu Jan 1 00:00:00 1970 From: Milan Broz Date: Wed, 14 Jul 2010 09:43:49 +0000 Subject: Re: [PATCH] HAL: Ignore internal DM devices with new DM udev rules Message-Id: <4C3D86D5.5050309@redhat.com> List-Id: References: <1279022894-20089-1-git-send-email-mbroz@redhat.com> In-Reply-To: <1279022894-20089-1-git-send-email-mbroz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On 07/14/2010 11:12 AM, Robby Workman wrote: > On Tue, 13 Jul 2010 14:08:14 +0200 > Milan Broz wrote: > I get two separate dialog windows to enter the passphrase > (the first appears, I enter the passphrase, and then the > second appears), and after entering the passphrase for the > second time, I get this: sigh. If udev rule set this flag, it is not top-level device and nobody should touch it. Top level device is then visible, that's the one you want to mount... if you see the log, event comes there for top-level: 04:04:20.064 [D] osspec.c:249: Found a dm-device (/dev/dm-6), mark it 04:04:20.064 [I] osspec.c:256: SEQNUM"50, ACTION=change, SUBSYSTEM=block, DEVPATH=/sys/devices/virtual/block/dm-6, DEVNAME=/dev/dm-6, IFINDEX=0 so I do not think it is problem with this patch. But in fact I have no idea how the whole desktop machinery above that works, I expect that there is some race with another auto mount system - see dmsetup table if the device is not mapped elsewhere already:-) Milan