From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Xiong Zhou <xzhou@redhat.com>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2] overlay/030: test immutable and append-only upper files
Date: Thu, 6 Apr 2017 11:45:57 +0800 [thread overview]
Message-ID: <20170406034557.GG22845@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1491394167-31409-1-git-send-email-amir73il@gmail.com>
On Wed, Apr 05, 2017 at 03:09:27PM +0300, Amir Goldstein wrote:
> Run the t_immutable test program for immutable/append-only files
> and directories in an overlayfs upper directory.
>
> This test is similar and was derived from generic/079, but
> the original test is _notrun on overlay mount because FS_IOC_GETFLAGS
> FS_IOC_SETFLAGS ioctls fail on overlay directory inodes.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> ---
> tests/generic/079 | 6 ++---
> tests/overlay/030 | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/overlay/030.out | 5 ++++
> tests/overlay/group | 1 +
> 4 files changed, 81 insertions(+), 4 deletions(-)
> create mode 100755 tests/overlay/030
> create mode 100644 tests/overlay/030.out
>
> Eryu,
>
> Here is v2 with fixes to your comments.
>
> I also changed generic/079 to use modern _require_* statements.
> and removed _scratch_unmount from its cleanup callback.
Thanks! But it'd be better to have two patches, one for new case and one
for 079 cleanup.
Thanks,
Eryu
prev parent reply other threads:[~2017-04-06 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 10:47 [PATCH 1/2] fstests: _require_chattr() must get an input arg Amir Goldstein
2017-04-05 10:47 ` [PATCH 2/2] overlay/030: test immutable and append-only upper files Amir Goldstein
2017-04-05 11:57 ` Eryu Guan
2017-04-05 12:09 ` [PATCH v2] " Amir Goldstein
2017-04-06 3:45 ` 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=20170406034557.GG22845@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 \
--cc=xzhou@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