linux-ext4 - Re: [OOPS]: Kernel 3.1 (ext3?)

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] [day] [month] [year] [list]

Date:	Tue, 22 Nov 2011 06:42:49 -0500
From:	Andrew Watts <akwatts@...il.com>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [OOPS]: Kernel 3.1 (ext3?)

On Tue, Nov 15, 2011 at 10:05:25AM -0600, Christoph Lameter wrote:
> On Mon, 14 Nov 2011, Jan Kara wrote:
> 
> > On Thu 10-11-11 08:29:37, Andrew Watts wrote:
> > > I had the following kernel panic today on 3.1 (machine was compiling code
> > > unattended). It would appear to be a bug/regression introduced sometime
> > > between 2.6.39.4 and 3.1.
> >   Hmm, the report is missing a line (top one) saying why the kernel
> > actually crashed. Can you add that?
> >
> >   Also it seems you are using SLUB allocator, right? This seems like a
> > problem there so adding some CCs.
> 
> Likely some data corruption. Enable slub debugging by passing
> 
> slub_debug
> 
> on the kernel commandline please to get some information as to where and
> when this happens.
> 

Hi Christoph.

Thank you for your reply. I'll enable slub debugging and post anything of
interest.

~ Andy

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html