[lkml]   [2007]   [May]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Race free attributes in sysfs
On Sat, May 26, 2007 at 12:12:02PM -0400, Bill Davidsen wrote:
> 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}.

It can happen if the attributes are added after the device is created,
so you need to add your attributes to the default groups before it is
registered with the driver core.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-05-27 11:17    [W:0.056 / U:5.408 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site