linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Giuseppe Scrivano <gscrivan@redhat.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org
Subject: [PATCH 0/2] Prepare for running unionmount testssuite from
Date: Wed, 15 Apr 2020 15:01:32 +0300	[thread overview]
Message-ID: <20200415120134.28154-1-amir73il@gmail.com> (raw)

Vivek,

You mentioned the need to run unionmount tests on custom layers
(virtiofs in your case) and I provided you the /etc/fstab solution,
which you said works for you.

I now added a new way to run unionmount tests on custom layers,
which I am going to use for xfstests integration [1].

I'd be interested to know if this method serves your use case as well.

Note that I overloaded the meaning of configuring base/lower/upper path:
  1. Use path different than the default
  2. Do not mount tmpfs nor unmount this path

I realize that it might have been better to split the two meanings into
different config options.  However, I am not fond of maintaining config
permutations that nobody is using.  So unless a user comes forward with
a use case, that's the way I intend to leave it.

Would love to get comments from anyone else of course.

Would love to get testing feedback from people that use the --fuse option,
because I am not testing it regularly.

Thanks,
Amir.

[1] https://github.com/amir73il/xfstests/commits/unionmount

Amir Goldstein (2):
  Stop using bind mounts for --samefs
  Configure custom layers via environment variables

 README           | 11 +++++++
 mount_union.py   |  8 ++---
 run              |  3 +-
 set_up.py        | 84 +++++++++++++++++++++++++++---------------------
 settings.py      | 61 +++++++++++++++++++++++++----------
 unmount_union.py | 19 ++++++-----
 6 files changed, 117 insertions(+), 69 deletions(-)

-- 
2.17.1


             reply	other threads:[~2020-04-15 12:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 12:01 Amir Goldstein [this message]
2020-04-15 12:01 ` [PATCH 1/2] Stop using bind mounts for --samefs Amir Goldstein
2020-04-15 12:01 ` [PATCH 2/2] Configure custom layers via environment variables Amir Goldstein
2020-04-15 15:30   ` Vivek Goyal
2020-04-15 16:27     ` Amir Goldstein
2020-04-15 19:42       ` Vivek Goyal
2020-04-16  7:10         ` Amir Goldstein
2020-04-16 12:58           ` Vivek Goyal
2020-04-16 13:49             ` Amir Goldstein
2020-04-18  9:57               ` Amir Goldstein
2020-04-20 19:14                 ` Vivek Goyal
2020-04-21  5:57                   ` Amir Goldstein
2020-05-17  8:45                     ` Amir Goldstein
2020-05-22 14:36                       ` Vivek Goyal
2020-05-22 17:19                         ` Amir Goldstein
2020-05-24 10:28                           ` Amir Goldstein
2020-05-26 12:54                             ` Vivek Goyal

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=20200415120134.28154-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=gscrivan@redhat.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vgoyal@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;
as well as URLs for NNTP newsgroup(s).