From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.39-rc0: umount tmpfs hangs
Date: Mon, 21 Mar 2011 05:54:13 +0000 [thread overview]
Message-ID: <20110321055413.GT22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <AANLkTinKPfYdbAQWuzi5Wf-HadLfjT0hmDnMwJwkwf8N@mail.gmail.com>
On Mon, Mar 21, 2011 at 08:30:23AM +0300, Alexander Beregalov wrote:
> > rcu_barrier() hanging for some reason... ??I really wonder what's going
> > on there - missing rcu_read_unlock()? ??Could you try to reproduce that
> > sucker and, if possible, bisect it?
>
> Yes, it's reproducible, but I'm bisecting another issue and have few
> more such issues with the current kernel.
Could you post the reproducer? Simple mounting tmpfs and umount explicitly
doesn't seem to trigger it; doing some IO on that fs doesn't change that,
ditto for umount done by shutdown instead of doing it manually...
next prev parent reply other threads:[~2011-03-21 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 2:24 2.6.39-rc0: umount tmpfs hangs Alexander Beregalov
2011-03-21 3:39 ` Al Viro
2011-03-21 5:30 ` Alexander Beregalov
2011-03-21 5:54 ` Al Viro [this message]
2011-03-21 6:18 ` Alexander Beregalov
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=20110321055413.GT22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=a.beregalov@gmail.com \
--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