>
> On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
> > On Nov 15, 2007 5:27 AM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > On Wed, 2007-11-14 at 20:19 +0100, Jiri Kosina wrote:
> > > > On Wed, 14 Nov 2007, Kay Sievers wrote:
> > > >
> > > > > Could it be an init-order problem, where something tries to use the
> > > > > block subsystem? Before it is initialized with:
> > > > > block/genhd.c :: subsys_initcall(genhd_device_init);
> > > > > If that's the case, we have an old bug that nobody noticed with static
> > > > > structures, which are zeroed that time, but definitely not properly
> > > > > initialized. I'll try to build loop non-modular now, and see if that
> > > > > makes the bug appear here.
> > >
> > > > my .config with which I reproduc this on 2.6.24-rc2-mm1 reliably can be
> > > > obtained from
http://www.jikos.cz/jikos/junk/.config
> > >
> > > Hmm, that config doesn't do anything here, and if I make it boot, it
> > > does not show the bug.
> > >
> > > Could you possibly enable kobject debugging and see if that exposes
> > > something, maybe something goes wrong with the kset refcount and it gets
> > > released while in use.
> > >
> > Hi,
> > I would do that.
>
> That would be great.
>
> > BTW, The bug report as EIP at __list_add with CONFIG_DEBUG_LIST=y
>
> Yeah, that hints that the kset, which contains the list, is not
> allocated at the time it is used, or it is already released (kfree)
> again by some buggy logic.
>
> All this could not happen before, as the kset was statically in memory.
> It may be an old bug, that just never crashed anything. We already fixed
> a bunch of similar things, that showed up while doing this patch set.
>
