From: Amir Goldstein <amir73il@gmail.com>
To: linux-unionfs@vger.kernel.org
Cc: Miklos Szeredi <miklos@szeredi.hu>
Subject: [ANNOUNCE] unionmount-testsuite: master branch updated to 95be14e
Date: Fri, 18 Dec 2020 12:38:54 +0200 [thread overview]
Message-ID: <20201218103854.10440-1-amir73il@gmail.com> (raw)
Hi All,
The master branch on the unionmount-testsuite tree [1] has been updated.
Changes in this update:
- Support for user configurable mount option
- Prepare to run tests with "userxattr" mount option
The previous update brought the ability for users to configure custom paths
with a custom filesystem for the underlying layers.
That ability was used to add xfstests wrappers for unionmount-testsuite.
This update brings the ability for users to configure custom overlay mount
options. This feature is also intended to be used by xfstests [2].
I used this ability to run tests with the new "userxattr" and "uuid=off"
mount option:
$ export UNIONMOUNT_MNTOPTIONS=userxattr
$ ./run --ov --verify
TEST rmdir.py:64: Remove populated directory
- rmtree /mnt/a/dir106
OSError: [Errno 5] Input/output error: '/mnt/a/dir106/pop'
$ export UNIONMOUNT_BASEDIR=/vdf # (xfs filesystem)
$ ./run --ov --verify
TEST hard-link-sym.py:10: Hard link symlink
./run --link /vdf/m/a/direct_sym100 /vdf/m/a/no_foo100
/vdf/m/a/no_foo100: inode number/layer changed on copy up...
$ export UNIONMOUNT_MNTOPTIONS="uuid=off"
$ ./run --ov --verify
and came to the following observations:
1) rmdir test as well as other tests involving opaque dir are failing
on tmpfs, because tmpfs does not support user.* xattrs
2) hard-link-sym test fails consistent inode number verification also
on xfs, because symlink does not support user.* xattrs
3) All the other tests pass on xfs with the userxattr mount option
4) No failures observed with uuid=off
I did not try to run tests inside non init userns.
This practice is left to the reader.
Thanks,
Amir.
[1] https://github.com/amir73il/unionmount-testsuite
[2] https://github.com/amir73il/xfstests/commits/unionmount
The head of the master branch is commit:
95be14e Allow user provided options with or without -o
Amir Goldstein (3):
Add support for user defined mount options
Let "userxattr" mount option in UNIONMOUNT_MNTOPTIONS imply --xdev
Allow user provided options with or without -o
mount_union.py | 6 ++--
remount_union.py | 4 +--
run | 90 ++++++++++++++++++++++++++++++------------------
settings.py | 15 +++++---
tool_box.py | 18 ++++++++++
5 files changed, 91 insertions(+), 42 deletions(-)
--
2.25.1
reply other threads:[~2020-12-18 10:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201218103854.10440-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).