From: Michal Hocko <mhocko@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: lockdep splat due to reclaim recursion detected
Date: Fri, 7 Oct 2016 12:52:45 +0200 [thread overview]
Message-ID: <20161007105245.GK18439@dhcp22.suse.cz> (raw)
In-Reply-To: <20161007103039.GJ9806@dastard>
On Fri 07-10-16 21:30:39, Dave Chinner wrote:
> On Fri, Oct 07, 2016 at 10:13:40AM +0200, Michal Hocko wrote:
> > Fix up xfs ML address
> >
> > On Fri 07-10-16 10:07:39, Michal Hocko wrote:
> > > Hi Dave,
> > > while playing with the test case you have suggested [1], I have hit the
> > > following lockdep splat. This is with mmotm git tree [2] but I didn't
> > > get to retest with the current linux-next (or any other tree of your
> > > preference) so there is a chance that something is broken in my tree so
> > > take this as a heads up. As soon as I am done with testing of the patch
> > > in the above email thread I will retest with linux-next.
> ....
> > > [ 61.878792] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Debian-1.8.2-1 04/01/2014
> > > [ 61.878792] 0000000000000000 ffff88001c8b3718 ffffffff81312f78 ffffffff825d99d0
> > > [ 61.878792] ffff88001cd04880 ffff88001c8b3750 ffffffff811260d1 000000000000000a
> > > [ 61.878792] ffff88001cd05178 ffff88001cd04880 ffffffff81095395 ffff88001cd04880
> > > [ 61.878792] Call Trace:
> > > [ 61.878792] [<ffffffff81312f78>] dump_stack+0x68/0x92
> > > [ 61.878792] [<ffffffff811260d1>] print_usage_bug.part.26+0x25b/0x26a
> > > [ 61.878792] [<ffffffff81095395>] ? print_shortest_lock_dependencies+0x17f/0x17f
> > > [ 61.878792] [<ffffffff81096074>] mark_lock+0x381/0x56d
> > > [ 61.878792] [<ffffffff810962be>] mark_held_locks+0x5e/0x74
> > > [ 61.878792] [<ffffffff8109875c>] lockdep_trace_alloc+0xaf/0xb2
> > > [ 61.878792] [<ffffffff8117d0f7>] kmem_cache_alloc_trace+0x3a/0x270
> > > [ 61.878792] [<ffffffff81169454>] ? vm_map_ram+0x2d2/0x4a6
> > > [ 61.878792] [<ffffffff8116924b>] ? vm_map_ram+0xc9/0x4a6
> > > [ 61.878792] [<ffffffff81169454>] vm_map_ram+0x2d2/0x4a6
> > > [ 61.878792] [<ffffffffa0051069>] _xfs_buf_map_pages+0xae/0x10b [xfs]
> > > [ 61.878792] [<ffffffffa0052cd0>] xfs_buf_get_map+0xaa/0x24f [xfs]
> > > [ 61.878792] [<ffffffffa0081d10>] xfs_trans_get_buf_map+0x144/0x2ef [xfs]
>
> Aw, come on! I explained this lockdep annotation bug a couple of
> days ago.
>
> https://www.spinics.net/lists/linux-fsdevel/msg102588.html
Ohh, I have missed that one. I have only seen one message from that
thread which landed in my inbox but didn't get to see the full thread.
Sorry about the noise then!
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2016-10-07 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161007080739.GD18439@dhcp22.suse.cz>
2016-10-07 8:13 ` lockdep splat due to reclaim recursion detected Michal Hocko
2016-10-07 10:30 ` Dave Chinner
2016-10-07 10:52 ` Michal Hocko [this message]
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=20161007105245.GK18439@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.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).