linux-kernel - Re: list corruption in the last few days. (block ? crypto ?)

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: <20110805171607.GA11703@redhat.com>
Date:	Fri, 5 Aug 2011 13:16:07 -0400
From:	Dave Jones <davej@...hat.com>
To:	Christoph Lameter <cl@...ux.com>
Cc:	Pekka Enberg <penberg@...nel.org>,
	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <jaxboe@...ionio.com>
Subject: Re: list corruption in the last few days. (block ? crypto ?)

On Fri, Aug 05, 2011 at 12:01:38PM -0500, Christoph Lameter wrote:
 > On Fri, 5 Aug 2011, Dave Jones wrote:
 > 
 > > On Fri, Aug 05, 2011 at 11:47:56AM -0500, Christoph Lameter wrote:
 > >  > On Fri, 5 Aug 2011, Dave Jones wrote:
 > >  >
 > >  > > Not sure if you were addressing my original report (quoted above), or the networking
 > >  > > related report in this part of the thread. But anyway, I had it turned on (as well as just about
 > >  > > every other debugging option).  I didn't see anything output from it though,
 > >  > > just the LIST_DEBUG warnings.
 > >  >
 > >  > But CONFIG_SLUB_DEBUG_ON was off? If slab debugging was on then this could
 > >  > be an issue with full slab list management instead of partial lists.
 > >
 > > $ grep SLUB_DEBUG_ON .config
 > > CONFIG_SLUB_DEBUG_ON=y
 > 
 > Argh another debugging code issue. Anyone who sees this please verify that
 > it also occurs with debugging off. I ran this code for 9 months in
 > various configs but only sporadically with debugging support since that
 > switches the lockless stuff.

This started turning up immediately as soon as it got merged to mainline.
Which leads me to believe no-one is running -next with debugging on either.
Perhaps we should force debugging on for a week once per release cycle.

	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/