linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Al Viro <viro@zeniv.linux.org.uk>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Maxim Patlasov <mpatlasov@virtuozzo.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Does anyone have test cases for mount namespaces?
Date: Wed, 8 Feb 2017 18:13:30 -0500	[thread overview]
Message-ID: <20170208231330.534fg6naiefldw6f@thunk.org> (raw)

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!"  :-)

Thanks,

						- Ted

             reply	other threads:[~2017-02-08 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 23:13 Theodore Ts'o [this message]
2017-02-09  2:55 ` Does anyone have test cases for mount namespaces? Eryu Guan
2017-02-09  5:09   ` Zorro Lang

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=20170208231330.534fg6naiefldw6f@thunk.org \
    --to=tytso@mit.edu \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mpatlasov@virtuozzo.com \
    --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).