From: Dave Jones <davej@redhat.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jaxboe@fusionio.com>
Subject: Re: list corruption in the last few days. (block ? crypto ?)
Date: Fri, 5 Aug 2011 14:20:09 -0400 [thread overview]
Message-ID: <20110805182008.GA22314@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108051312090.28580@router.home>
On Fri, Aug 05, 2011 at 01:14:50PM -0500, Christoph Lameter wrote:
> 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.
http://codemonkey.org.uk/junk/adamo.config
Dave
next prev parent reply other threads:[~2011-08-05 18:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 1:00 list corruption in the last few days. (block ? crypto ?) Dave Jones
2011-08-05 8:46 ` Markus Trippelsdorf
2011-08-05 9:13 ` Pekka Enberg
2011-08-05 9:22 ` Jens Axboe
2011-08-05 9:33 ` Pekka Enberg
2011-08-05 16:32 ` Christoph Lameter
2011-08-05 16:39 ` Dave Jones
2011-08-05 16:47 ` Christoph Lameter
2011-08-05 16:51 ` Dave Jones
2011-08-05 17:01 ` Christoph Lameter
2011-08-05 17:16 ` Dave Jones
2011-08-05 18:14 ` Christoph Lameter
2011-08-05 18:20 ` Dave Jones [this message]
2011-08-06 19:31 ` Linus Torvalds
2011-08-07 13:15 ` Pekka Enberg
2011-08-07 18:58 ` Pekka Enberg
2011-08-07 21:13 ` Linus Torvalds
2011-08-08 5:18 ` Pekka Enberg
2011-08-08 6:12 ` Linus Torvalds
2011-08-08 6:15 ` Xiaotian Feng
2011-08-08 6:14 ` Xiaotian Feng
2011-08-08 6:16 ` Pekka Enberg
2011-08-08 6:34 ` Xiaotian Feng
2011-08-08 6:18 ` Pekka Enberg
2011-08-08 6:31 ` Xiaotian Feng
2011-08-08 6:38 ` Pekka Enberg
2011-08-08 9:18 ` Xiaotian Feng
2011-08-08 14:58 ` Christoph Lameter
2011-08-07 20:36 ` Pekka Enberg
2011-08-05 9:00 ` Xiaotian Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110805182008.GA22314@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=penberg@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox