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-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fscrypt updates for 5.7
Date: Mon, 30 Mar 2020 09:53:59 -0700 [thread overview]
Message-ID: <20200330165359.GA1895@sol.localdomain> (raw)
The following changes since commit 98d54f81e36ba3bf92172791eba5ca5bd813989b:
Linux 5.6-rc4 (2020-03-01 16:38:46 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus
for you to fetch changes up to 861261f2a9cc488c845fc214d9035f7a11094591:
ubifs: wire up FS_IOC_GET_ENCRYPTION_NONCE (2020-03-19 21:57:06 -0700)
----------------------------------------------------------------
Add an ioctl FS_IOC_GET_ENCRYPTION_NONCE which retrieves a file's
encryption nonce. This makes it easier to write automated tests which
verify that fscrypt is doing the encryption correctly.
----------------------------------------------------------------
Eric Biggers (4):
fscrypt: add FS_IOC_GET_ENCRYPTION_NONCE ioctl
ext4: wire up FS_IOC_GET_ENCRYPTION_NONCE
f2fs: wire up FS_IOC_GET_ENCRYPTION_NONCE
ubifs: wire up FS_IOC_GET_ENCRYPTION_NONCE
Documentation/filesystems/fscrypt.rst | 11 +++++++++++
fs/crypto/fscrypt_private.h | 20 ++++++++++++++++++++
fs/crypto/keysetup.c | 16 ++--------------
fs/crypto/policy.c | 21 ++++++++++++++++++++-
fs/ext4/ioctl.c | 6 ++++++
fs/f2fs/file.c | 11 +++++++++++
fs/ubifs/ioctl.c | 4 ++++
include/linux/fscrypt.h | 6 ++++++
include/uapi/linux/fscrypt.h | 1 +
9 files changed, 81 insertions(+), 15 deletions(-)
next reply other threads:[~2020-03-30 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 16:53 Eric Biggers [this message]
2020-03-31 21:50 ` [GIT PULL] fscrypt updates for 5.7 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=20200330165359.GA1895@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=linux-mtd@lists.infradead.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).