Messages in this thread | | | Date | Thu, 11 Feb 2010 11:10:38 +0900 | From | Tejun Heo <> | Subject | Re: [PATCH] sysfs: differentiate between locking links and non-links |
| |
Hello,
On 02/11/2010 10:31 AM, Eric W. Biederman wrote: >> I think some code dynamically creates attributes today, as this has >> never been a restriction. >> >> So I don't know if this is going to work :( > > I need to see how locks do this, but they face the same problem. For > normal locks this is resolved by having a requirement to call a special > initializer in the dynamic case. Adding that requirement for the > rare dynamically allocated sysfs attributes seems reasonable.
Yeah, this is the same problem all other constructus face too and the reason why different variants of initializers are introduced for lockdep support. For dynamic ones, making the initializer declare static key and using it to initialize lockdep_map should work.
> Additionally sysfs attributes are exactly the right granularity for > lock classes because that is where the behavior is the same or > changes.
Yeap.
> We have 845 instances of static struct attributes which certainly makes > that the dominant case and worth aiming at.
Yeah, and sysfs will be following the usual convention of dealing with these issues, which is the right thing to do.
Thanks.
-- tejun
| |