linux-kernel - Re: kernel BUG at mm/slab.c:610

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: <84144f020703140341p322d9dc5wb9edc37bf923685d@mail.gmail.com>
Date:	Wed, 14 Mar 2007 12:41:51 +0200
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"Marco Berizzi" <pupilla@...mail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: kernel BUG at mm/slab.c:610

Hi Marco,

On 3/14/07, Marco Berizzi <pupilla@...mail.com> wrote:
> Hello everybody. Sorry for posting to this list, but I'm pretty lost.

Don't worry, this is the proper mailing list for bug reports.

On 3/14/07, Marco Berizzi <pupilla@...mail.com> wrote:
> I don't think this is related to buggy hardware because it is happening
> on 3 different boxes with the same hardware config.

No, looks like someone is feeding a bad pointer to slab. The debug
check is relatively new and in previous kernels the problem would
might have gone unnoticed causing silent corruption of the slab.

On 3/14/07, Marco Berizzi <pupilla@...mail.com> wrote:
> ksymoops 2.4.10 on i686 2.6.20.  Options used

>From Documentation/oops-tracing.txt:

"NOTE: ksymoops is useless on 2.6.  Please use the Oops in its original format
 (from dmesg, etc).  Ignore any references in this or other docs to "decoding
 the Oops" or "running it through ksymoops".  If you post an Oops from 2.6 that
 has been run through ksymoops, people will just tell you to repost it."

So, can you please repost the original oops? Also, please enable
CONFIG_DEBUG_SLAB  and try to reproduce. Thanks.
-
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/