Messages in this thread | | | Date | Fri, 5 Aug 2011 13:14:50 -0500 (CDT) | From | Christoph Lameter <> | 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.
| |