From: Zorro Lang <zlang@redhat.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Al Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Maxim Patlasov <mpatlasov@virtuozzo.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Does anyone have test cases for mount namespaces?
Date: Thu, 9 Feb 2017 13:09:56 +0800 [thread overview]
Message-ID: <20170209050956.GA14570@dhcp12-143.nay.redhat.com> (raw)
In-Reply-To: <20170209025523.GC1946@eguan.usersys.redhat.com>
On Thu, Feb 09, 2017 at 10:55:23AM +0800, Eryu Guan wrote:
> Hi Ted,
>
> On Wed, Feb 08, 2017 at 06:13:30PM -0500, Theodore Ts'o wrote:
> > Hi,
> >
> > I'm trying to backport a security fix involving the mount namespaces
> > (in fs/pnode.c), and I'm wondering if anyone has a set of sanity
> > checks (ideally in the form of a shell script) which they use to make
> > sure nothing has broken with respect to mount --make-shared, et. al.
> >
> > I've really gotten spoiled with xfstests, and the mount namespaces
> > code looks subtle and quick to anger, and I'd prefer to have something
> > more substantial than "It builds! Release it to production!" :-)
>
> AFAIK, there's a test script from LTP does some mount namespace function
> and regression tests, e.g. --bind --make-private --make-shared --move
>
> $LTP_SOURCE/testscripts/test_fs_bind.sh
>
> And Zorro Lang has proposed some mount tests[1] for xfstests last May,
> but the tests never got reviewed & merged (hope they can be reviewed &
> committed by this opportunity :).
>
> Thanks,
> Eryu
>
> [1] https://www.spinics.net/lists/fstests/msg03029.html
If Ted or someone would like to review these patches, I really
appreciate that :)
Thanks,
Zorro
prev parent reply other threads:[~2017-02-09 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 23:13 Does anyone have test cases for mount namespaces? Theodore Ts'o
2017-02-09 2:55 ` Eryu Guan
2017-02-09 5:09 ` Zorro Lang [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=20170209050956.GA14570@dhcp12-143.nay.redhat.com \
--to=zlang@redhat.com \
--cc=ebiederm@xmission.com \
--cc=guaneryu@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatlasov@virtuozzo.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).