[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200711051403.39479.mb@bu3sch.de>
Date: Mon, 5 Nov 2007 14:03:38 +0100
From: Michael Buesch <mb@...sch.de>
To: "Pekka Enberg" <penberg@...helsinki.fi>
Cc: "Peter Zijlstra" <peterz@...radead.org>,
"Luis R. Rodriguez" <mcgrof@...il.com>,
"Michael Wu" <flamingice@...rmilk.net>,
linux-wireless <linux-wireless@...r.kernel.org>,
"John W. Linville" <linville@...driver.com>,
"Ingo Molnar" <mingo@...hat.com>,
"Johannes Berg" <johannes@...solutions.net>,
linux-kernel@...r.kernel.org, "Michael Chan" <mchan@...adcom.com>,
netdev@...r.kernel.org, "Christoph Lameter" <clameter@....com>
Subject: Re: RFC: Reproducible oops with lockdep on count_matching_names()
On Monday 05 November 2007 13:23:50 Pekka Enberg wrote:
> Hi Michael,
>
> On Sat, 2007-11-03 at 21:06 +0100, Michael Buesch wrote:
> > Who is responsible for slab btw?
> > I mean, someone should be interested in getting this bug fixed. :)
> > When using slab I see random corruptions. I think related to rmmod, but
> > I'm not sure. I don't see this with slub.
>
> Is CONFIG_DEBUG_SLAB enabled? Usually these kind of random corruptions
> are caused by someone passing a bad pointer to kfree() or
> kmem_cache_free().
Yeah.
What I also saw was random "one-bit-errors" once and then on rmmod of modules.
I have absolutely no idea how they were caused, though (I read the freeing
codes of the stuff hundreds of times). I don't have any of the oops messages
anymore.
But I do _not_ see this behaviour with slub anymore.
--
Greetings Michael.
-
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