From: Eryu Guan <eguan@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic: test mount move semantics
Date: Fri, 22 Sep 2017 15:38:47 +0800 [thread overview]
Message-ID: <20170922073847.GC8034@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170921082423.22710-1-zlang@redhat.com>
On Thu, Sep 21, 2017 at 04:24:23PM +0800, Zorro Lang wrote:
> This's a functional test case for mount --move operation, it verifies
> below semantics:
>
> ---------------------------------------------------------------------------
> | MOVE MOUNT OPERATION |
> |**************************************************************************
> |source(A)->| shared | private | slave | unbindable |
> | dest(B) | | | | |
> | | | | | | |
> | v | | | | |
> |**************************************************************************
> | shared | shared | shared | shared & slave | invalid |
> | | | | | |
> |non-shared| shared | private | slave | unbindable |
> ***************************************************************************
> NOTE: moving a mount residing under a shared mount is invalid.
>
> This case uses fsstress to produce a little random load, to make
> sure basic operations won't break the the moved mountpoints.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
Thanks for the test! As what we discussed just now, the --move semantics
test is hard to follow, please add more comments inline to describe your
test steps and purpose.
Thanks,
Eryu
next prev parent reply other threads:[~2017-09-22 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 8:24 [PATCH] generic: test mount move semantics Zorro Lang
2017-09-22 7:38 ` Eryu Guan [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-30 6:53 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=20170922073847.GC8034@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.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