From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] fsverity updates for 6.2
Date: Sun, 11 Dec 2022 20:48:35 -0800 [thread overview]
Message-ID: <Y5ayo48TtNrPgU9D@sol.localdomain> (raw)
The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:
Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fsverity-for-linus
for you to fetch changes up to a4bbf53d88c728da9ff6c316b1e4ded63a8f3940:
fsverity: simplify fsverity_get_digest() (2022-11-29 21:07:41 -0800)
----------------------------------------------------------------
The main change this cycle is to stop using the PG_error flag to track
verity failures, and instead just track failures at the bio level. This
follows a similar fscrypt change that went into 6.1, and it is a step
towards freeing up PG_error for other uses.
There's also one other small cleanup.
----------------------------------------------------------------
Eric Biggers (2):
fsverity: stop using PG_error to track error status
fsverity: simplify fsverity_get_digest()
fs/ext4/readpage.c | 8 ++----
fs/f2fs/compress.c | 64 +++++++++++++++++++++-----------------------
fs/f2fs/data.c | 53 ++++++++++++++++++++++--------------
fs/verity/fsverity_private.h | 5 ++++
fs/verity/hash_algs.c | 6 +++++
fs/verity/measure.c | 19 ++-----------
fs/verity/verify.c | 12 ++++-----
7 files changed, 85 insertions(+), 82 deletions(-)
next reply other threads:[~2022-12-12 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 4:48 Eric Biggers [this message]
2022-12-13 5:00 ` [GIT PULL] fsverity updates for 6.2 pr-tracker-bot
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=Y5ayo48TtNrPgU9D@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).