linux-kernel - Re: 2.6.24-rc2-mm1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a8e1da0711141911h52b4e91bo86c07073d5dd2c6d@mail.gmail.com>
Date:	Thu, 15 Nov 2007 11:11:10 +0800
From:	"Dave Young" <hidave.darkstar@...il.com>
To:	"Kay Sievers" <kay.sievers@...y.org>
Cc:	"Jiri Kosina" <jikos@...os.cz>, "Greg KH" <greg@...ah.com>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.24-rc2-mm1

On Nov 15, 2007 10:38 AM, Kay Sievers <kay.sievers@...y.org> wrote:
>
> On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
> > On Nov 15, 2007 5:27 AM, Kay Sievers <kay.sievers@...y.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.
>
Now with the DEBUG_KOBJECT set , nothing more info.
But this time the EIP is at the strnlen (called by printk -- line 239
of kobject.c)

EIP is at strnlen +0x9/0x20
EAX 6b6b6b6b EBX c05487c14 ecx 6b6b6b6b EDX fffffffe
---cut---

If you need more infomation, I will copy more (no camera in hand)

Regards
dave
-
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/