From: Eric Biggers <ebiggers@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2 0/2] generic/577: fix hash check and add metadata cleaning
Date: Thu, 3 Nov 2022 23:52:31 -0700 [thread overview]
Message-ID: <Y2S2r2hStHK47xdR@sol.localdomain> (raw)
In-Reply-To: <20221103191420.390048-1-aalbersh@redhat.com>
On Thu, Nov 03, 2022 at 08:14:18PM +0100, Andrey Albershteyn wrote:
> Hi all,
>
> This patchset has two fixes for generic/577. The first one is fix of
> common helper _fsv_have_hash_algorithm which didn't work correctly in
> generic/577 as that test requires signing. The second patch fixes issue
> which is uncovered when first patch is applied. The test fails to write to file
> with already enabled verity.
>
> v1 -> v2:
> - add first patch as proper fix
>
> Andrey Albershteyn (2):
> common/verity: disable signature verification on hash alg check
> generic/577: add missing fsverity metadata cleaning
>
> common/verity | 3 +++
> tests/generic/577 | 1 +
> 2 files changed, 4 insertions(+)
>
Thanks Andrey! One thing that you overlooked is that _fsv_have_hash_algorithm()
needs to restore the previous value of fs.verity.require_signatures, not the
value that existed at the beginning of the test.
Also, I found that some of the newer tests don't work properly on systems where
fs.verity.require_signatures=1. I'd like to fix that too.
Can you take a look at the patchset
https://lore.kernel.org/fstests/20221104064742.167326-1-ebiggers@kernel.org/T/#u
I just sent out? It should take care of everything...
- Eric
prev parent reply other threads:[~2022-11-04 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 19:14 [PATCH v2 0/2] generic/577: fix hash check and add metadata cleaning Andrey Albershteyn
2022-11-03 19:14 ` [PATCH v2 1/2] common/verity: disable signature verification on hash alg check Andrey Albershteyn
2022-11-03 19:14 ` [PATCH v2 2/2] generic/577: add missing fsverity metadata cleaning Andrey Albershteyn
2022-11-04 6:52 ` Eric Biggers [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=Y2S2r2hStHK47xdR@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