public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/5] overlay mount tests
Date: Tue, 11 Jul 2017 22:52:01 +0300	[thread overview]
Message-ID: <1499802726-11045-1-git-send-email-amir73il@gmail.com> (raw)

Eryu,

overlayfs-next brings some changes of mount behavior described at [1].
Some of the changes depend on the new inodes index opt-in feature and
some don't.

The new test overlay/035 checks for overlay mount behaviors, which are
already present in upstream.

The new test overlay/036 checks for new overlay mount behaviors related
to exclusivity of upper and work dirs among overlay mounts. This test
is expected to fail on upstream kernel, but for a good reason, because
the mount configurations that it tests (sharing upper dir among two
overlay mounts) are not wise at all.

The old test overlay/014 is modified to work well with current upstream
kernel as well as with overlayfs-next with inodes index enabled.

I have one more test for the overlay/mount group to test specific behavior
with index=on, but holding it back until Miklos picks up a patch that fixes
one of the mount verifications that is currently broken on overlayfs-next.

Thanks,
Amir.

[1] https://github.com/amir73il/linux/commit/9412812ef54861081904f24ddaf176b957b98d40

Amir Goldstein (5):
  overlay/014: remove unneeded require and include
  overlay/014: fix test with inodes index enabled
  overlay: create overlay/mount test group
  overlay: test cases that force read-only mount
  overlay: test mount error cases with exclusive directories

 tests/overlay/014     |  7 ++---
 tests/overlay/035     | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/overlay/035.out |  5 +++
 tests/overlay/036     | 82 ++++++++++++++++++++++++++++++++++++++++++++++++
 tests/overlay/036.out |  3 ++
 tests/overlay/group   |  6 ++--
 6 files changed, 184 insertions(+), 6 deletions(-)
 create mode 100755 tests/overlay/035
 create mode 100644 tests/overlay/035.out
 create mode 100755 tests/overlay/036
 create mode 100644 tests/overlay/036.out

-- 
2.7.4

             reply	other threads:[~2017-07-11 19:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 19:52 Amir Goldstein [this message]
2017-07-11 19:52 ` [PATCH 1/5] overlay/014: remove unneeded require and include Amir Goldstein
2017-07-11 19:52 ` [PATCH 2/5] overlay/014: fix test with inodes index enabled Amir Goldstein
2017-07-12 10:36   ` Eryu Guan
2017-07-12 10:45     ` Amir Goldstein
2017-07-11 19:52 ` [PATCH 3/5] overlay: create overlay/mount test group Amir Goldstein
2017-07-11 19:52 ` [PATCH 4/5] overlay: test cases that force read-only mount Amir Goldstein
2017-07-12 10:31   ` Eryu Guan
2017-07-12 10:37     ` Amir Goldstein
2017-07-11 19:52 ` [PATCH 5/5] overlay: test mount error cases with exclusive directories Amir Goldstein
2017-07-12 10:47   ` Eryu Guan
2017-07-12 11:08     ` Amir Goldstein
2017-07-12 11:46       ` Eryu Guan
2017-07-12 11:53         ` Amir Goldstein
2017-07-12 12:07   ` [PATCH v2 " Amir Goldstein

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=1499802726-11045-1-git-send-email-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --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