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

[Christoph Lameter]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/