Subject: Re: Race between "mount" uevent and /proc/mounts?
From: Xavier Bestel <xavier.bestel@free.fr>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Al Viro <viro@ftp.linux.org.uk>, Sergey Vlasov <vsu@altlinux.ru>,
       Roderich.Schupp.extern@mch.siemens.de, linux-kernel@vger.kernel.org,
       linux-hotplug-devel@lists.sourceforge.net
In-Reply-To: <20051026143417.GA18949@vrfy.org>
References: <0AD07C7729CA42458B22AFA9C72E7011C8EF@mhha22kc.mchh.siemens.de>
	 <20051025140041.GO7992@ftp.linux.org.uk>
	 <20051026142710.1c3fa2da.vsu@altlinux.ru>
	 <20051026111506.GQ7992@ftp.linux.org.uk>  <20051026143417.GA18949@vrfy.org>
Content-Type: text/plain
Message-Id: <1130337932.3340.1.camel@capoeira>
Mime-Version: 1.0
Date: Wed, 26 Oct 2005 16:45:32 +0200
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 874
Lines: 22

On Wed, 2005-10-26 at 16:34, Kay Sievers wrote:

> They are actually events for claim/release of a block device. As uevents
> are bound to kobjects we needed to send these events from an existing device
> which is the blockdev itself.
> 
> Sure, the event itself, has nothing to do with a filesystem. The names are
> like this for historical reasons and "CLAIM/RELEASE" may be less confusing.
> The events are used as a trigger to rescan /proc/mounts instead of polling
> it constantly.
> 
> If you have a better idea where to plug it, or if we better rename it, we
> should do that...

Make /proc/mount send an inotify event ?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/