[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46585C52.7020808@tmr.com>
Date: Sat, 26 May 2007 12:12:02 -0400
From: Bill Davidsen <davidsen@....com>
To: linux-kernel@...r.kernel.org
Cc: Mark Lord <lkml@....ca>, Dmitry Torokhov <dtor@...ightbb.com>,
Pierre Ossman <drzeus-list@...eus.cx>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Race free attributes in sysfs
Greg KH wrote:
> On Wed, May 23, 2007 at 09:27:12AM -0400, Mark Lord wrote:
>> Greg KH wrote:
>>> And yes, it only starts to look for things when it recieves an event, it
>>> does not "scan" sysfs at all.
>> Does it "look for" only that one event, or does it "scan" at that point?
>
> udev will act on that event, and as I mentioned, not read anything from
> sysfs at all, unless a custom rule is in the rules file asking it to
> read a specific sysfs file in the tree.
>
> So no "scanning" happens unless specificically asked for.
>
> And as mentioned, udev can work just fine without sysfs enabled at all
> now, with the exception of some custom rules for some devices.
>
I think what Mark is asking is about the case where udev gets an event,
is told to look in sysfs, and while looking encounters a partially
described device.
Now that the "this won't happen unless..." cases, could someone cover
this and state that it either can't happen because {reason} or that if
it does the result will be {description}.
--
Bill Davidsen <davidsen@....com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists