From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Race free attributes in sysfs
Date: Sun, 20 May 2007 13:01:31 +0200 [thread overview]
Message-ID: <46502A8B.70803@drzeus.cx> (raw)
Hi Greg,
I'm reworking the sysfs stuff in the MMC layer to be a bit more flexible, but
there is one thing that has me baffled; how do you add attributes to an object
in a race free manner when you have a dynamic set of attributes.
I've looked at other parts of the kernel and they all use:
1. Add object.
2. Add attributes.
To me, it seems like there's a window between 1 and 2 where the object is in
/sys but doesn't have the proper attributes. Life for user space gets very
annoying if it has to add artificial delays to avoid this window.
So how do I do this properly? Something like this would, from my point of view,
be the sane method:
1. Add hidden object.
2. Add attributes.
3. Show object.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next reply other threads:[~2007-05-20 11:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 11:01 Pierre Ossman [this message]
2007-05-21 3:12 ` Race free attributes in sysfs Dmitry Torokhov
2007-05-21 7:47 ` Pierre Ossman
2007-05-22 21:24 ` Mark Lord
2007-05-23 2:43 ` Dmitry Torokhov
2007-05-23 4:21 ` Greg KH
2007-05-23 13:27 ` Mark Lord
2007-05-23 15:14 ` Greg KH
2007-05-26 16:12 ` Bill Davidsen
2007-05-27 8:57 ` Greg KH
2007-05-21 17:50 ` Kay Sievers
2007-05-21 18:43 ` Pierre Ossman
2007-05-21 19:28 ` Kay Sievers
2007-05-22 8:38 ` Cornelia Huck
2007-05-23 4:25 ` Greg KH
2007-05-22 15:40 ` Pierre Ossman
2007-05-22 15:58 ` Kristian Høgsberg
2007-05-22 21:25 ` Mark Lord
2007-05-23 4:24 ` Greg KH
2007-05-23 5:44 ` Pierre Ossman
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=46502A8B.70803@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox