public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v3 0/5] Overlayfs exportfs tests
Date: Sun, 28 Jan 2018 18:59:01 +0800	[thread overview]
Message-ID: <20180128105901.GP18267@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1517131356-8048-1-git-send-email-amir73il@gmail.com>

On Sun, Jan 28, 2018 at 11:22:31AM +0200, Amir Goldstein wrote:
> Eryu,
> 
> Assuming you did not get to reviewing the overlay/exportfs
> v2 patches yet, here is a better version for you to test/review,
> which I had tested with various OVERLAY_MOUNT_OPTIONS variants.

I haven't started looking at them yet..

> 
> NFS export support patches are now on overlayfs-next and all
> overlay/exportfs tests are expected to pass with overlayfs-next and
> default kernel configuration.

Thanks for all revisions, testings and information! I'll go through all
your pending overlay patches next week.

Thanks,
Eryu

      parent reply	other threads:[~2018-01-28 10:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28  9:22 [PATCH v3 0/5] Overlayfs exportfs tests Amir Goldstein
2018-01-28  9:22 ` [PATCH v3 1/5] fstests: implement require of multiple overlayfs features Amir Goldstein
2018-01-29 14:33   ` Eryu Guan
2018-01-29 17:06     ` Amir Goldstein
2018-01-30  4:52       ` Eryu Guan
2018-01-28  9:22 ` [PATCH v3 2/5] overlay: test encode/decode overlay file handles Amir Goldstein
2018-01-29 14:39   ` Eryu Guan
2018-01-29 17:23     ` Amir Goldstein
2018-01-30  4:54       ` Eryu Guan
2018-01-28  9:22 ` [PATCH v3 3/5] overlay: test encode/decode of non-samefs " Amir Goldstein
2018-01-28  9:22 ` [PATCH v3 4/5] overlay: test encode/decode overlay file handles with renames Amir Goldstein
2018-01-28  9:22 ` [PATCH v3 5/5] overlay: test encode/decode of non-samefs " Amir Goldstein
2018-01-28 10:59 ` Eryu Guan [this message]

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=20180128105901.GP18267@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=amir73il@gmail.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