public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Omer Zilberberg <Omer.Zilberberg@netapp.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/4[13,62]: restore TEST mount options
Date: Tue, 31 Oct 2017 07:36:58 +1100	[thread overview]
Message-ID: <20171030203658.GA4094@dastard> (raw)
In-Reply-To: <20171030080831.7339-1-Omer.Zilberberg@netapp.com>

On Mon, Oct 30, 2017 at 10:08:31AM +0200, Omer Zilberberg wrote:
> These tests locally change the TEST_FS_MOUNT_OPTS/MOUNT_OPTIONS
> environment variables, and run _test_cycle_mount. As a result, following
> tests using the TEST mount point may start with different mount options,
> depending on run order.

I don't think that's the case. The change of the environment
variable should only affect the current test process and it's
children. When the test exits, we go back to the environment of the
check process, where the TEST_FS_MOUNT_OPTS environment variable is
still correctly set, and all future tests inherit from that. i.e.:

$ export FOO=foo
$ echo $FOO
foo
$ bash
$ echo $FOO
foo
$ export FOO=bar
$ echo $FOO
bar
$ exit
$ echo $FOO
foo
$

And after each test, check runs _check_filesystems(), which cycles
the test mount, so for each new test process that is run they should
already start in the correct state...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2017-10-30 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  8:08 [PATCH] generic/4[13,62]: restore TEST mount options Omer Zilberberg
2017-10-30 20:36 ` Dave Chinner [this message]
2017-10-31  4:37   ` Eryu Guan
2017-10-31 10:25     ` Omer Zilberberg
2017-10-31 11:34       ` Eryu Guan
2017-11-01 12:06         ` Omer Zilberberg
2017-11-01 12:52           ` Eryu Guan
2017-11-01 15:03             ` Omer Zilberberg
2017-11-02 12:13               ` Eryu Guan
2017-11-05 14:20                 ` Omer Zilberberg
2017-10-31 22:08     ` Dave Chinner

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=20171030203658.GA4094@dastard \
    --to=david@fromorbit.com \
    --cc=Omer.Zilberberg@netapp.com \
    --cc=fstests@vger.kernel.org \
    /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