public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 12:51:20 -0400	[thread overview]
Message-ID: <20110805165119.GA11593@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108051146180.28580@router.home>

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

	Dave


  reply	other threads:[~2011-08-05 16:52 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 [this message]
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
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=20110805165119.GA11593@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