[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090205152630.GB4099@kroah.com>
Date: Thu, 5 Feb 2009 07:26:30 -0800
From: Greg KH <greg@...ah.com>
To: "Zhao, Yu" <yu.zhao@...el.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
balajirrao@...il.com, laurent.riffard@...e.fr,
balajirrao@...nmoko.org
Subject: Re: linux-next: Tree for March 7: slab corruptions
On Thu, Feb 05, 2009 at 03:27:28PM +0800, Zhao, Yu wrote:
> Greg KH wrote:
>> On Thu, Feb 05, 2009 at 01:08:51PM +0800, Zhao, Yu wrote:
>>> Hi Greg,
>>>
>>> It looks like following fix is not in Linus' tree. Can you please queue
>>> it?
>>>
>>> http://lkml.org/lkml/2008/3/8/155
>> Queue what? That is a message from over a year ago, are you seeing a
>> problem in mainline in this area? If so, do you have a proposed fix for
>> it?
>
> Yes, I'm seeing 'kobject (ffff8800bf03b908): tried to init an initialized
> object, something is seriously wrong'. The warning is fired when
> re-initializing
> a kobject that has been deleted while its state remains `initialized'.
What kobject is causing this to happen?
kobjects should not be static, which it sounds like is the root of your
problem here. If they are properly dynamic, this can not happen.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists