From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Fixes to overlayfs immutable files tests
Date: Sun, 6 Jun 2021 19:00:16 +0300 [thread overview]
Message-ID: <CAOQ4uxj=ztE5kyE62dS=UrLzt--E7Gwucab_r+k4Jgg+nEpt1g@mail.gmail.com> (raw)
In-Reply-To: <20210606151811.420788-1-amir73il@gmail.com>
On Sun, Jun 6, 2021 at 6:18 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> Eryu,
>
> Test overlay/075 was written and merged to track a known overlayfs issue
> which exists in current upstream.
>
> The introduction of fileattr operations in kernel v5.13-rc1 by Miklos
> has paved the way for the fix patch that I recently posted [1].
>
> Patch #1 fixes a test bug that was hiding behind the known issue in
> upstream kernel.
Oh, you already merged this one. Great.
There is no change from v1 to v2, so you may ignore it and review
patch #2 for next week.
Thanks,
Amir.
>
> Patch #2 add test coverage to part of the kernel fix patch that is not
> covered by the current test.
>
> Thanks,
> Amir.
>
> [1] https://lore.kernel.org/linux-unionfs/20210606144641.419138-1-amir73il@gmail.com/
>
> Amir Goldstein (2):
> overlay/075: fix wrong invocation of t_immutable
> overlay/075: add test coverage for clearing immutable/append-only
> flags
>
> tests/overlay/075 | 23 +++++++++++++++++++----
> 1 file changed, 19 insertions(+), 4 deletions(-)
>
> --
> 2.31.1
>
prev parent reply other threads:[~2021-06-06 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 15:18 [PATCH v2 0/2] Fixes to overlayfs immutable files tests Amir Goldstein
2021-06-06 15:18 ` [PATCH v2 1/2] overlay/075: fix wrong invocation of t_immutable Amir Goldstein
2021-06-06 15:18 ` [PATCH v2 2/2] overlay/075: add test coverage for clearing immutable/append-only flags Amir Goldstein
2021-06-06 16:00 ` Amir Goldstein [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='CAOQ4uxj=ztE5kyE62dS=UrLzt--E7Gwucab_r+k4Jgg+nEpt1g@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).