[lkml]   [2007]   [May]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Race free attributes in sysfs
    Pierre Ossman wrote:
    > Kay Sievers wrote:
    >> We could change the driver-core to suppress the creation of an attribute
    >> if the attribute's show() or store() method returns something like
    >> -ENOENT at registration time?
    >> The driver would pass _all_ possible attributes of the device at
    >> registration time, but the core would only create the attributes which
    >> are implemented for this particular device? Would that work for you?
    > Not sure. Not in an obvious way at least.
    > It also doesn't feel like "the kernel way". Generally you can
    > create/allocate an object, assign attributes to it, then activate it.
    > Couldn't it be done so that I can add sysfs stuff to a device after I
    > just initialized it? (but before I add it).
    >> You can assign any number of attribute groups to the device. If they
    >> don't have a group name, they will all be created directly at the device
    >> level. Would that work for you?
    > I've had a look at sysfs groups and the biggest beef I have with those
    > is that they're too low level. In order to use them I first need to
    > create device attributes, then create an array of pointers to each attr
    > member. It would be nice if I could just feed an array of device
    > attributes (i.e. I want wrappers).

    And how does this help to avoid the race condition?
    Just curious.
    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-22 23:29    [W:0.032 / U:3.472 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site