Messages in this thread |  | | Subject | Re: [PATCH] kobject: set state_initialized to 0 in kobject_cleanup | From | "Wu, Songjun" <> | Date | Wed, 2 Nov 2016 09:29:06 +0800 |
| |
On 11/1/2016 22:56, Greg KH wrote: > On Tue, Nov 01, 2016 at 06:41:44PM +0800, Songjun Wu wrote: >> If state_initialized is not set to 0 when a kobject is >> released, a device is registered, unregistered, and >> registered again, the error below will occur. >> >> kobject (dec04bb0): tried to init an initialized object, >> something is seriously wrong. > > Yes, your code is wrong, don't try to change the kernel core to work > around it :) > > That message is there for a reason, and this patch has been rejected > many times in the past. kobjects can NOT ever be reused, and should > never be static (but yes, there are lots of in-kernel users with static > kobjects, they just never get reused...) > > What code is emitting this message? I'll be glad to help you fix it up > if you can point me at it. > Thank you very much. I will not use the static kobjects to fix the error. :) > thanks, > > greg k-h >
|  |