From: Jens Axboe <jaxboe@fusionio.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>
Subject: Re: list corruption in the last few days. (block ? crypto ?)
Date: Fri, 5 Aug 2011 11:22:05 +0200 [thread overview]
Message-ID: <4E3BB63D.8030801@fusionio.com> (raw)
In-Reply-To: <CAOJsxLEMf8SbSmJv5u6GZtq_OYH3fpmomT-ioWXQGp83veK7wQ@mail.gmail.com>
On 2011-08-05 11:13, Pekka Enberg wrote:
> On Fri, Aug 5, 2011 at 11:46 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
>> On 2011.08.04 at 21:00 -0400, Dave Jones wrote:
>>> Sometime in the last week, something was merged which causes my laptop
>>> to lock up occasionally. I can trigger it most of the time just by
>>> doing a kernel build. When it gets to the final linking stage, it locks up hard.
>>>
>>> I finally managed to coax something out of usb console to get the traces below,
>>> which seem to implicate something in the block layer ?
>>>
>>> my root device is an lvm volume on an dmcrypt'd block dev, which might be relevant,
>>> as I don't see this happening on other machines with simpler setups.
>>>
>>> I'm going to try bisecting, but it might take me a few days, because it's
>>> such a pain in the ass to reproduce this reliably.
>>>
>>> [ 5913.233035] ------------[ cut here ]------------
>>> [ 5913.233097] WARNING: at lib/list_debug.c:53 __list_del_entry+0x8d/0x98()
>>> [ 5913.233101] Hardware name: Adamo 13
>>> [ 5913.233105] list_del corruption. prev->next should be ffffea000434fd20, but was ffffea0004199520
>>
>> See also: http://lkml.org/lkml/2011/8/3/37
>
> That's in networking so SLUB lockless patches are almost certainly the
> issue here. Is this with SLUB debugging enabled or not? Christoph, it
> like the partial lists are getting corrupted somehow.
I knew it was you, Perks!
:-)
--
Jens Axboe
next prev parent reply other threads:[~2011-08-05 9:22 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 [this message]
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
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=4E3BB63D.8030801@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=davej@redhat.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