From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Paul Menage <menage@google.com>,
containers@lists.osdl.org, Arjan van de Ven <arjan@infradead.org>
Subject: Re: [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2()
Date: Mon, 9 Feb 2009 09:34:14 +0000 [thread overview]
Message-ID: <20090209093414.GU28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20090209004046.3ce1dde0.akpm@linux-foundation.org>
On Mon, Feb 09, 2009 at 12:40:46AM -0800, Andrew Morton wrote:
> > Thread 1:
> > for ((; ;))
> > {
> > mount -t cgroup -o cpuset xxx /mnt > /dev/null 2>&1
> > mkdir /mnt/0 > /dev/null 2>&1
> > rmdir /mnt/0 > /dev/null 2>&1
> > umount /mnt > /dev/null 2>&1
> > }
> >
> > Thread 2:
> > {
> > mount -t cpuset xxx /mnt > /dev/null 2>&1
> > umount /mnt > /dev/null 2>&1
> > }
How cute... Same mountpoint in both, so these mount(2) will sometimes
fail (cgroup picks the same sb on the same options, AFAICS) and fail
silently due to these redirects...
That's a lovely way to stress-test a large part of ro-bind stuff *and*
umount()-related code. Could you do C equivalent of the above (just
the same syscalls in loop, nothing fancier) and do time-stamped strace?
next prev parent reply other threads:[~2009-02-09 9:34 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 [this message]
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
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=20090209093414.GU28946@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