From: Eric Biggers <ebiggers@kernel.org>
To: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: linux-fscrypt@vger.kernel.org, Yunlei He <heyunlei@hihonor.com>,
bintian.wang@hihonor.com
Subject: [PATCH 0/2] fs-verity: fix error handling in ->end_enable_verity()
Date: Tue, 2 Mar 2021 12:04:18 -0800 [thread overview]
Message-ID: <20210302200420.137977-1-ebiggers@kernel.org> (raw)
Fix some bugs in how ext4_end_enable_verity() and
f2fs_end_enable_verity() handle failure to enable verity on the file.
This is intended to supersede the f2fs patch from Yunlei He
(https://lore.kernel.org/r/20210302113850.17011-1-heyunlei@hihonor.com,
https://lore.kernel.org/r/20210301141506.6410-1-heyunlei@hihonor.com,
https://lore.kernel.org/r/c1ce1421-2576-5b48-322c-fa682c7510d7@kernel.org).
I fixed the same bugs in ext4 too, reworked the functions to cleanly
separate the success and error paths, and improved the commit message.
These patches can be taken independently via the ext4 and f2fs trees.
I've just sent them out together since they're similar.
Eric Biggers (2):
ext4: fix error handling in ext4_end_enable_verity()
f2fs: fix error handling in f2fs_end_enable_verity()
fs/ext4/verity.c | 90 ++++++++++++++++++++++++++++++------------------
fs/f2fs/verity.c | 61 +++++++++++++++++++++-----------
2 files changed, 97 insertions(+), 54 deletions(-)
--
2.30.1
next reply other threads:[~2021-03-03 4:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 20:04 Eric Biggers [this message]
2021-03-02 20:04 ` [PATCH 1/2] ext4: fix error handling in ext4_end_enable_verity() Eric Biggers
2021-03-11 15:36 ` Theodore Ts'o
2021-03-02 20:04 ` [PATCH 2/2] f2fs: fix error handling in f2fs_end_enable_verity() Eric Biggers
2021-03-05 1:37 ` [f2fs-dev] " Chao Yu
2021-03-05 4:52 ` 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=20210302200420.137977-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=bintian.wang@hihonor.com \
--cc=heyunlei@hihonor.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@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;
as well as URLs for NNTP newsgroup(s).