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
Subject: Re: Race between "mount" uevent and /proc/mounts?
Date: Wed, 26 Oct 2005 14:45:32 +0000 [thread overview]
Message-ID: <1130337932.3340.1.camel@capoeira> (raw)
In-Reply-To: <20051026143417.GA18949@vrfy.org>
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 ?
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
WARNING: multiple messages have this Message-ID (diff)
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
Subject: Re: Race between "mount" uevent and /proc/mounts?
Date: Wed, 26 Oct 2005 16:45:32 +0200 [thread overview]
Message-ID: <1130337932.3340.1.camel@capoeira> (raw)
In-Reply-To: <20051026143417.GA18949@vrfy.org>
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 ?
next prev parent reply other threads:[~2005-10-26 14:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 13:20 Race between "mount" uevent and /proc/mounts? Schupp Roderich (extern) BenQ MD PD SWP 2 CM MCH
2005-10-25 14:00 ` Al Viro
2005-10-26 10:27 ` Sergey Vlasov
2005-10-26 10:27 ` Sergey Vlasov
2005-10-26 11:15 ` Al Viro
2005-10-26 11:15 ` Al Viro
2005-10-26 14:34 ` Kay Sievers
2005-10-26 14:34 ` Kay Sievers
2005-10-26 14:45 ` Xavier Bestel [this message]
2005-10-26 14:45 ` Xavier Bestel
2005-10-26 19:28 ` Al Viro
2005-10-26 19:28 ` Al Viro
2005-11-01 0:28 ` Kay Sievers
2005-11-01 0:28 ` Kay Sievers
2005-11-01 3:58 ` Kay Sievers
2005-11-01 3:58 ` Kay Sievers
2005-11-01 19:54 ` Sergey Vlasov
2005-11-01 19:54 ` Sergey Vlasov
2005-11-01 21:35 ` Kay Sievers
2005-11-01 21:35 ` Kay Sievers
2005-11-02 13:01 ` Sergey Vlasov
2005-11-02 13:01 ` Sergey Vlasov
2005-11-03 8:07 ` Al Viro
2005-11-03 8:07 ` Al Viro
2005-11-03 10:52 ` Sergey Vlasov
2005-11-03 10:52 ` Sergey Vlasov
2005-11-03 11:30 ` Al Viro
2005-11-03 11:30 ` Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1130337932.3340.1.camel@capoeira \
--to=xavier.bestel@free.fr \
--cc=Roderich.Schupp.extern@mch.siemens.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
--cc=vsu@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.