Hello, Alan. Alan Stern wrote: > Tejun: > > Can you look at this oops message please? It appears similar to the > sysfs bug in 2.6.23-rc1, but it occurred under 2.6.22. Is a similar > fix needed for the 2.6.22-stable series?
2.6.23-rc1 bug was one too many put during symlink creation failure path leading to premature release of parent kobject on removal. The posted log looks more like premature module unload. For example, something like... 1. module b uses services of module a 2. module b creates some attributes with struct attribute in the module 3. module b unloads but attr created in #2 is not removed 4. module a tries to unload and tries to remove attr from #2 and oops because struct attribute referenced by the attr is already gone. Thanks. -- tejun - 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/
