From: Al Viro <viro@ZenIV.linux.org.uk>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: containers@lists.osdl.org, Paul Menage <menage@google.com>,
Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2()
Date: Fri, 13 Feb 2009 05:47:51 +0000 [thread overview]
Message-ID: <20090213054751.GI28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4995007D.7040101@cn.fujitsu.com>
On Fri, Feb 13, 2009 at 01:09:17PM +0800, Li Zefan wrote:
> I ran following testcase, and triggered the warning in 1 hour:
>
> thread 1:
> for ((; ;))
> {
> mount --bind /cgroup /mnt > /dev/null 2>&1
> umount /mnt > /dev/null 2>&1
> }
>
> tread 2:
> for ((; ;))
> {
> mount -t cgroup -o cpu xxx /cgroup > /dev/null 2>&1
> mkdir /cgroup/0 > /dev/null 2>&1
> rmdir /cgroup/0 > /dev/null 2>&1
> umount -l /cgroup > /dev/null 2>&1
> }
Wow. You know, at that point these redirects could probably be removed.
If anything in there ends up producing an output, we very much want to
see that. Actually, I'd even make that
mount --bind /cgroup/mnt || (echo mount1: ; date)
etc., so we'd see when do they fail and which one fails (if any)...
Which umount has failed in the above, BTW?
next prev parent reply other threads:[~2009-02-13 5:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 3:23 [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2() Li Zefan
2009-02-09 8:40 ` Andrew Morton
2009-02-09 8:49 ` Li Zefan
2009-02-09 11:03 ` Al Viro
2009-02-09 11:58 ` Al Viro
2009-02-10 5:47 ` Li Zefan
2009-02-09 9:34 ` Al Viro
2009-02-09 11:30 ` Li Zefan
2009-02-12 6:10 ` Li Zefan
2009-02-12 6:24 ` Al Viro
2009-02-12 6:33 ` Li Zefan
2009-02-12 6:54 ` Li Zefan
2009-02-12 7:07 ` Al Viro
2009-02-13 5:09 ` Li Zefan
2009-02-13 5:47 ` Al Viro [this message]
2009-02-13 6:12 ` Li Zefan
2009-02-13 6:31 ` Li Zefan
2009-02-13 6:41 ` Al Viro
2009-02-13 7:18 ` Al Viro
2009-02-13 7:26 ` Li Zefan
2009-02-16 1:29 ` Li Zefan
2009-02-16 2:38 ` Al Viro
2009-02-16 2:47 ` Li Zefan
2009-02-16 2:57 ` Al Viro
2009-02-09 17:48 ` Dave Hansen
2009-02-09 18:11 ` Arjan van de Ven
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=20090213054751.GI28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
/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