While thinking about locking schema
with respect to sysfs files I recalled,
why I implemented such a logic -
now one can _always_ remove _any_ module
[corresponding object is removed from accessible
pathes and waits untill all exsting users are gone],
which is very good - I really like it in networking model,
while with whole device driver model
if we will read device's file very quickly
in several threads we may end up not unloading it at all.
So decision is simple from the first point of view -
just remove appropriate objects from accessible pathes
and free them from finall callbacks [device's remove method].
Evgeniy Polyakov
Only failure makes us experts. -- Theo de Raadt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
