linux-kernel - Re: [2.6.25-rc2-mm1] Oops in _

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]

Date:	Tue, 4 Mar 2008 14:51:40 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Jiri Slaby" <jirislaby@...il.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linux kernel mailing list" <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org, "Jan Sonnek" <xsonnek@...muni.cz>,
	"Christoph Lameter" <clameter@....com>
Subject: Re: [2.6.25-rc2-mm1] Oops in __kmalloc

On Tue, Mar 4, 2008 at 12:41 PM, Jiri Slaby <jirislaby@...il.com> wrote:
>  >> while booting up a notebook on 32 bit, this oopses appeared on the console
>  >> after ext3 fsck:
>  >> http://www.fi.muni.cz/~xslaby/sklad/mem_oops/
>  >>
>  >> It's 2.6.25-rc2-mm1, I can't find similar reports, is this known or hardware
>  >> issue (unlikely, 2.6.24.2 seems to be OK)?
>  >
>  > I don't recall seeing a similar report and yes, it'll be a kernel bug.
>  >
>  > We've fixed a few things and it could be that this will just go away in
>  > next -mm.  If it doesn't, a bisection search would be good, thanks.
>
>  Well, next -mm is out. Could you test, Jan? [our -mm git is up-to-date]

I don't see your config but if you have CONFIG_SLUB enabled, this is
probably the same problem as:

http://bugzilla.kernel.org/show_bug.cgi?id=10015

which is fixed since 2.6.25-rc2 in mainline.

                              Pekka
--
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/