From: Eric Biggers <ebiggers@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/577: add missing fsverity metadata cleaning
Date: Wed, 2 Nov 2022 15:41:38 -0700 [thread overview]
Message-ID: <Y2LyIiDDR9/RS773@sol.localdomain> (raw)
In-Reply-To: <20221102165134.169135-1-aalbersh@redhat.com>
On Wed, Nov 02, 2022 at 05:51:34PM +0100, Andrey Albershteyn wrote:
> When fs-verity is enabled on the file, file becomes read-only. In last
> check, test tries to empty the file. However, fs-verity denies
> opening/writing to file.
>
> Remove file beforehand as in other checks.
>
> Signed-off-by: Andrey Albershteyn <aalbersh@redhat.com>
> ---
> tests/generic/577 | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/generic/577 b/tests/generic/577
> index 98c3888f..916f3be3 100755
> --- a/tests/generic/577
> +++ b/tests/generic/577
> @@ -121,6 +121,7 @@ if _fsv_have_hash_algorithm sha512 $fsv_file; then
> fi
>
> echo -e "\n# Testing empty file"
> +reset_fsv_file
> echo -n > $fsv_file
> _fsv_sign $fsv_file $sigfile.emptyfile --key=$keyfile --cert=$certfile | \
> _filter_scratch
Thank you for reporting this. How did you notice this? This test actually is
currently passing, because there is another test bug that makes
_fsv_have_hash_algorithm always return false here. That really needs to be
fixed first, as otherwise your fix doesn't really do anything.
- Eric
next prev parent reply other threads:[~2022-11-02 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:51 [PATCH] generic/577: add missing fsverity metadata cleaning Andrey Albershteyn
2022-11-02 22:41 ` Eric Biggers [this message]
2022-11-03 10:23 ` Andrey Albershteyn
2022-11-03 16:34 ` Eric Biggers
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=Y2LyIiDDR9/RS773@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=aalbersh@redhat.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