From: Al Viro <viro@ZenIV.linux.org.uk>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Miklos Szeredi <mszeredi@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: 3.15-rc5 soft-lockup in dentry_kill
Date: Mon, 12 May 2014 16:42:30 +0100 [thread overview]
Message-ID: <20140512154230.GD18016@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+5PVA480wkD1xhWbhPVGoHeG=T3F3zeEwAPbEatUmmX_L5h-w@mail.gmail.com>
On Mon, May 12, 2014 at 09:21:53AM -0400, Josh Boyer wrote:
> Hi All,
>
> We got a report[1] of udevd hanging up in a soft lockup with 3.15-rc5
> over the weekend. The backtrace is below. I know there were a number
> of recent changes here, so hopefully this triggers someone's memory.
Reproducer would be nice... Incidentally, kernfs ->d_revalidate() looks
like a massive source of contention - it grabs a system-wide mutex all
the time, and I'd like to see profiles on the loads that go anywhere near
that sucker.
prev parent reply other threads:[~2014-05-12 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 13:21 3.15-rc5 soft-lockup in dentry_kill Josh Boyer
2014-05-12 15:42 ` Al Viro [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=20140512154230.GD18016@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--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