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: Thu, 3 Nov 2022 16:34:27 +0000 [thread overview]
Message-ID: <Y2PtkwvY0PfKuMpG@gmail.com> (raw)
In-Reply-To: <20221103102321.73kklwrpjmslyl5s@aalbersh.remote.csb>
On Thu, Nov 03, 2022 at 11:23:21AM +0100, Andrey Albershteyn wrote:
> On Wed, Nov 02, 2022 at 03:41:38PM -0700, Eric Biggers wrote:
> > 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.
>
> Hmm, it fails for me. _fsv_have_hash_algorithm also seems to work
> (returns 0), what bug do you mean? Don't see anything obvious.
>
> I was running -g verity on ext4/xfs (I'm working on adding fsverity
> support to xfs).
That's exciting that you're working on fsverity support for xfs! I wasn't aware
that someone was working on that.
If the test is failing even on ext4 for you, then you must have changed
something, either in the kernel or in the tests, that exposed the issue.
Anyway, for _fsv_have_hash_algorithm() to work properly, it needs to set the
fs.verity.require_signatures sysctl to 0 temporarily (if it was 1). I'll send
out a patch if you don't get to it first.
- Eric
prev parent reply other threads:[~2022-11-03 16:38 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
2022-11-03 10:23 ` Andrey Albershteyn
2022-11-03 16:34 ` 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=Y2PtkwvY0PfKuMpG@gmail.com \
--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