linux-unionfs mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Eric Biggers <ebiggers@google.com>,
	Alexander Larsson <alexl@redhat.com>,
	Leah Rumancik <leah.rumancik@gmail.com>,
	fstests@vger.kernel.org, linux-unionfs@vger.kernel.org,
	Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 0/3] fstests-bld overlayfs updates
Date: Sun, 27 Aug 2023 12:05:20 +0300	[thread overview]
Message-ID: <CAOQ4uxiuHfECh6ARBma86DbDCDzNPa1wCCxXLB9CRWQShj8q4g@mail.gmail.com> (raw)
In-Reply-To: <20230625135033.3205742-1-amir73il@gmail.com>

On Sun, Jun 25, 2023 at 4:50 PM Amir Goldstein <amir73il@gmail.com> wrote:
>
> Hi Ted,
>
> The first patch enables testing the new overlayfs verity feature,
> which is NOT the same as saying that overlayfs supports fsverity.
>
> The other two are cleanups and fixes to overlayfs configs.
>

Hi Ted,

Ping.

Did these two small patches get lost?

FYI, Alexander's overlayfs verity patches are queued for 6.6
and his overlay/verity fstests have already been merged to
fstests release v2023.07.23.

It would be great if fstests-bld support to test this feature would
be merged as well.

Thanks,
Amir.

>
> Amir Goldstein (3):
>   test-appliance: enable verity for testing overlay over ext4
>   test-appliance: remove redudant overlay configs
>   test-appliance: skip overlayfs tests from base fs exclude list
>
>  .../files/root/fs/overlay/cfg/large-ext4           | 14 --------------
>  test-appliance/files/root/fs/overlay/cfg/large-xfs | 14 --------------
>  .../files/root/fs/overlay/cfg/small-ext4           | 14 --------------
>  .../files/root/fs/overlay/cfg/small-ext4.exclude   |  1 -
>  test-appliance/files/root/fs/overlay/cfg/small-xfs | 14 --------------
>  .../files/root/fs/overlay/cfg/small-xfs.exclude    |  1 -
>  test-appliance/files/root/fs/overlay/config        |  2 +-
>  test-appliance/files/root/runtests.sh              |  1 +
>  8 files changed, 2 insertions(+), 59 deletions(-)
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/large-ext4
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/large-xfs
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/small-ext4
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/small-ext4.exclude
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/small-xfs
>  delete mode 100644 test-appliance/files/root/fs/overlay/cfg/small-xfs.exclude
>
> --
> 2.34.1
>

      parent reply	other threads:[~2023-08-27  9:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 13:50 [PATCH 0/3] fstests-bld overlayfs updates Amir Goldstein
2023-06-25 13:50 ` [PATCH 1/3] test-appliance: enable verity for testing overlay over ext4 Amir Goldstein
2023-06-25 13:50 ` [PATCH 2/3] test-appliance: remove redudant overlay configs Amir Goldstein
2023-06-25 13:50 ` [PATCH 3/3] test-appliance: skip overlayfs tests from base fs exclude list Amir Goldstein
2023-08-27  9:05 ` 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=CAOQ4uxiuHfECh6ARBma86DbDCDzNPa1wCCxXLB9CRWQShj8q4g@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=alexl@redhat.com \
    --cc=ebiggers@google.com \
    --cc=fstests@vger.kernel.org \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).