From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: 3.4.4-rt13: btrfs + xfstests 006 = BOOM.. and a bonus rt_mutex deadlock report for absolutely free!
Date: Thu, 12 Jul 2012 13:07:58 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1207121253170.32033@ionos> (raw)
In-Reply-To: <1342072060.7338.102.camel@marge.simpson.net>
On Thu, 12 Jul 2012, Mike Galbraith wrote:
> crash> struct rt_mutex 0xffff8801770601c8
> struct rt_mutex {
> wait_lock = {
> raw_lock = {
> slock = 7966
> }
> },
> wait_list = {
> node_list = {
> next = 0xffff880175eedbe0,
> prev = 0xffff880175eedbe0
> },
> rawlock = 0xffff880175eedbd8,
Urgh. Here is something completely wrong. That should point to
wait_lock, i.e. the rt_mutex itself, but that points into lala land.
> spinlock = 0x0
> },
> owner = 0x1,
> save_state = 0,
> file = 0x0,
> name = 0xffffffff81781b9b "&(&device->io_lock)->lock",
> line = 0,
> magic = 0x0
> }
> crash> struct list_head 0xffff880175eedbe0
> struct list_head {
> next = 0x6b6b6b6b6b6b6b6b,
> prev = 0x6b6b6b6b6b6b6b6b
> }
That's POISON_FREE. How the heck can this happen ?
> Reproducer2: dbench -t 30 8
>
> [ 692.857164]
> [ 692.857165] ============================================
> [ 692.863963] [ BUG: circular locking deadlock detected! ]
> [ 692.869264] Not tainted
> [ 692.871708] --------------------------------------------
> [ 692.877008] btrfs-delayed-m/1404 is deadlocking current task dbench/7937
> [ 692.877009]
> [ 692.885183]
> [ 692.885184] 1) dbench/7937 is trying to acquire this lock:
> [ 692.892149] [ffff88014d6aea80] {&(&eb->lock)->lock}
> [ 692.897102] .. ->owner: ffff880175808501
> [ 692.901018] .. held by: btrfs-delayed-m: 1404 [ffff880175808500, 120]
> [ 692.907657]
> [ 692.907657] 2) btrfs-delayed-m/1404 is blocked on this lock:
> [ 692.914797] [ffff88014bf58d60] {&(&eb->lock)->lock}
> [ 692.919751] .. ->owner: ffff880175186101
> [ 692.923672] .. held by: dbench: 7937 [ffff880175186100, 120]
> [ 692.930309]
> [ 692.930309] btrfs-delayed-m/1404's [blocked] stackdump:
Hrmm. Both locks are rw_locks and we prevent multiple readers for the
known reasons in RT. No idea how to deal with that one :(
Thanks,
tglx
next prev parent reply other threads:[~2012-07-12 11:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 5:47 3.4.4-rt13: btrfs + xfstests 006 = BOOM.. and a bonus rt_mutex deadlock report for absolutely free! Mike Galbraith
2012-07-12 8:44 ` Mike Galbraith
2012-07-12 9:53 ` Mike Galbraith
2012-07-12 11:43 ` Thomas Gleixner
2012-07-12 11:57 ` Mike Galbraith
2012-07-12 13:31 ` Thomas Gleixner
2012-07-12 13:37 ` Mike Galbraith
2012-07-12 13:43 ` Thomas Gleixner
2012-07-12 13:48 ` Mike Galbraith
2012-07-12 13:51 ` Mike Galbraith
2012-07-13 6:31 ` Mike Galbraith
2012-07-13 9:52 ` Thomas Gleixner
2012-07-13 10:14 ` Mike Galbraith
2012-07-13 10:26 ` Thomas Gleixner
2012-07-13 10:47 ` Chris Mason
2012-07-13 12:50 ` Mike Galbraith
2012-07-12 11:07 ` Thomas Gleixner [this message]
2012-07-12 17:09 ` Chris Mason
2012-07-13 10:04 ` Thomas Gleixner
2012-07-13 12:50 ` Chris Mason
2012-07-13 14:47 ` Thomas Gleixner
2012-07-14 10:14 ` Mike Galbraith
2012-07-15 17:56 ` Chris Mason
2012-07-16 2:02 ` Mike Galbraith
2012-07-16 16:02 ` Steven Rostedt
2012-07-16 16:26 ` Mike Galbraith
2012-07-16 16:35 ` Chris Mason
2012-07-16 16:36 ` Mike Galbraith
2012-07-16 17:03 ` Steven Rostedt
2012-07-17 4:18 ` Mike Galbraith
2012-07-17 4:27 ` Steven Rostedt
2012-07-17 4:34 ` Steven Rostedt
2012-07-17 4:46 ` Mike Galbraith
2012-07-17 4:44 ` Mike Galbraith
2012-07-17 12:54 ` Mike Galbraith
2012-07-16 10:55 ` Mike Galbraith
2012-07-16 15:43 ` Chris Mason
2012-07-16 16:16 ` Mike Galbraith
2012-07-14 13:38 ` Mike Galbraith
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=alpine.LFD.2.02.1207121253170.32033@ionos \
--to=tglx@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).