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: <alpine.DEB.2.00.1108051312090.28580@router.home>
Date:	Fri, 5 Aug 2011 13:14:50 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	Dave Jones <davej@...hat.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, 5 Aug 2011, Dave Jones wrote:

>  > 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.

I have run some tests over the last hours with kvm and
CONFIG_SLUB_DEBUG_ON as well as CONFIG_DEBUG_LIST set but (aside from
other unrelated backtraces in other subsystems) did not see this issue.

Can I get a .config? Maybe that will help.


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