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.6
Date: Sun, 27 Aug 2023 20:47:41 -0700 [thread overview]
Message-ID: <20230828034741.GB5028@sol.localdomain> (raw)
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -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 919dc320956ea353a7fb2d84265195ad5ef525ac:
fsverity: skip PKCS#7 parser when keyring is empty (2023-08-20 10:33:43 -0700)
----------------------------------------------------------------
Several cleanups for fs/verity/, including two commits that make the
builtin signature support more cleanly separated from the base feature.
----------------------------------------------------------------
Eric Biggers (4):
fsverity: explicitly check that there is no algorithm 0
fsverity: simplify handling of errors during initcall
fsverity: move sysctl registration out of signature.c
fsverity: skip PKCS#7 parser when keyring is empty
fs/verity/fsverity_private.h | 12 +++----
fs/verity/hash_algs.c | 8 +++++
fs/verity/init.c | 56 ++++++++++++++++++++------------
fs/verity/open.c | 18 +++--------
fs/verity/signature.c | 77 ++++++++++++++------------------------------
fs/verity/verify.c | 11 ++-----
6 files changed, 79 insertions(+), 103 deletions(-)
next reply other threads:[~2023-08-28 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 3:47 Eric Biggers [this message]
2023-08-28 20:15 ` [GIT PULL] fsverity updates for 6.6 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=20230828034741.GB5028@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).