From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: recursive locking (coredump/vfs_write)
Date: Fri, 22 Nov 2013 23:52:18 +0000 [thread overview]
Message-ID: <20131122235217.GK10323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20131122211156.GA7520@quack.suse.cz>
On Fri, Nov 22, 2013 at 10:11:56PM +0100, Jan Kara wrote:
> Hi,
>
> On Wed 13-11-13 16:11:47, Dave Jones wrote:
> > here's another one..
> >
> >
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 3.12.0+ #2 Not tainted
> > ---------------------------------------------
> > trinity-child3/13302 is trying to acquire lock:
> > (sb_writers#5){.+.+.+}, at: [<ffffffff811b7013>] vfs_write+0x173/0x1f0
> >
> > but task is already holding lock:
> > (sb_writers#5){.+.+.+}, at: [<ffffffff8122006d>] do_coredump+0xf1d/0x1070
> Thanks for report. Attached patch should fix this. Al, can you please
> merge it?
No. It's already fixed in mainline by commit 52da40.
next prev parent reply other threads:[~2013-11-22 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 21:11 recursive locking (coredump/vfs_write) Dave Jones
2013-11-15 10:18 ` Peter Wu
2013-11-22 21:11 ` Jan Kara
2013-11-22 23:52 ` Al Viro [this message]
2013-11-24 9:31 ` Jan Kara
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=20131122235217.GK10323@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=davej@redhat.com \
--cc=jack@suse.cz \
--cc=linux-kernel@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