Messages in this thread | | | Date | Thu, 15 Apr 2004 09:10:11 -0700 | From | Greg KH <> | Subject | Re: [RFC] fix sysfs symlinks |
| |
On Thu, Apr 15, 2004 at 04:19:42PM +0100, Russell King wrote: > > However, should I also mention about the possibility of the following > being in the same category; they are also typically statically > allocated... > > struct bus_type > struct class > struct platform_device > > I think these may be worse than struct device_driver because I don't > see their unregister functions even doing any form of "wait until > unused" - so rather than being deadlock prone, they're oops-prone. > > Sigh, sometimes life is <insert your favourite word to describe this>. ;(
Yeah, I agree. For 2.7, I want to make static allocation of anything that contains a kobject or kref not allowed to help fix things like this.
So once again we are back at the "module unload is hard" problem :)
thanks,
greg k-h - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |