From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Rajnoha Subject: Re: [PATCH 1/3] Send KOBJ_ADD event after dm resume ioctl. Date: Fri, 19 Mar 2010 14:24:22 +0100 Message-ID: <4BA37B06.1040107@redhat.com> References: <1268920694-10960-1-git-send-email-mbroz@redhat.com> <4BA29CA4.9070000@redhat.com> <20100319090656.GR6379@soda.linbit> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Kay Sievers Cc: device-mapper development List-Id: dm-devel.ids On 03/19/2010 10:24 AM, Kay Sievers wrote: > No, that's what "change" is for, and we already have these "change" > events for dm. Udev does not care if the device is ready or not, it > synchronizes /sys and /dev, and that works just fine with "change" > events. CHANGE events, not quite... We can't even rely on these. Just to mention, there's also a CHANGE event generated when read-only flag is set for a device (this is not managed by device-mapper of course). This one is generated even before the actual CHANGE event that is generated when DM device is ready to be used. Peter