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-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fsverity updates for 5.11
Date: Sun, 13 Dec 2020 21:53:27 -0800 [thread overview]
Message-ID: <X9b910/Ldj6kdljm@sol.localdomain> (raw)
The following changes since commit 09162bc32c880a791c6c0668ce0745cf7958f576:
Linux 5.10-rc4 (2020-11-15 16:44:31 -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 bde493349025ca0559e2fff88592935af3b8df19:
fs-verity: move structs needed for file signing to UAPI header (2020-11-23 19:30:14 -0800)
----------------------------------------------------------------
Some cleanups for fs-verity:
- Rename some names that have been causing confusion.
- Move structs needed for file signing to the UAPI header.
----------------------------------------------------------------
Eric Biggers (4):
fs-verity: remove filenames from file comments
fs-verity: rename fsverity_signed_digest to fsverity_formatted_digest
fs-verity: rename "file measurement" to "file digest"
fs-verity: move structs needed for file signing to UAPI header
Documentation/filesystems/fsverity.rst | 68 ++++++++++++++++------------------
fs/verity/enable.c | 8 ++--
fs/verity/fsverity_private.h | 36 ++----------------
fs/verity/hash_algs.c | 2 +-
fs/verity/init.c | 2 +-
fs/verity/measure.c | 12 +++---
fs/verity/open.c | 24 ++++++------
fs/verity/signature.c | 14 +++----
fs/verity/verify.c | 2 +-
include/uapi/linux/fsverity.h | 49 ++++++++++++++++++++++++
10 files changed, 116 insertions(+), 101 deletions(-)
next reply other threads:[~2020-12-14 5:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 5:53 Eric Biggers [this message]
2020-12-14 20:56 ` [f2fs-dev] [GIT PULL] fsverity updates for 5.11 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=X9b910/Ldj6kdljm@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@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 NNTP newsgroup(s).