From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: fsverity@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>
Subject: [GIT PULL] fsverity updates for 6.4
Date: Mon, 24 Apr 2023 23:27:07 -0700 [thread overview]
Message-ID: <20230425062707.GB77408@sol.localdomain> (raw)
The following changes since commit 197b6b60ae7bc51dd0814953c562833143b292aa:
Linux 6.3-rc4 (2023-03-26 14:40:20 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fsverity/linux.git tags/fsverity-for-linus
for you to fetch changes up to 04839139213cf60d4c5fc792214a08830e294ff8:
fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds (2023-04-11 19:23:23 -0700)
----------------------------------------------------------------
Several cleanups and fixes for fs/verity/, including a couple minor
fixes to the changes in 6.3 that added support for Merkle tree block
sizes less than the page size.
----------------------------------------------------------------
Eric Biggers (4):
fs/buffer.c: use b_folio for fsverity work
fsverity: use WARN_ON_ONCE instead of WARN_ON
fsverity: explicitly check for buffer overflow in build_merkle_tree()
fsverity: reject FS_IOC_ENABLE_VERITY on mode 3 fds
Luis Chamberlain (1):
fs-verity: simplify sysctls with register_sysctl()
fs/buffer.c | 9 ++++-----
fs/verity/enable.c | 21 +++++++++++++++++++--
fs/verity/hash_algs.c | 4 ++--
fs/verity/open.c | 2 +-
fs/verity/signature.c | 9 +--------
include/linux/fsverity.h | 6 +++---
6 files changed, 30 insertions(+), 21 deletions(-)
next reply other threads:[~2023-04-25 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 6:27 Eric Biggers [this message]
2023-04-26 17:06 ` [GIT PULL] fsverity updates for 6.4 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=20230425062707.GB77408@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--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).