From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: [PATCH 0/4] fscrypt: add ioctl to get file's encryption nonce
Date: Sat, 14 Mar 2020 13:50:48 -0700 [thread overview]
Message-ID: <20200314205052.93294-1-ebiggers@kernel.org> (raw)
This patchset adds an ioctl FS_IOC_GET_ENCRYPTION_NONCE which retrieves
the nonce from an encrypted file or directory.
This is useful for automated ciphertext verification testing.
See patch #1 for more details.
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(-)
base-commit: 98d54f81e36ba3bf92172791eba5ca5bd813989b
--
2.25.1
next reply other threads:[~2020-03-15 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 20:50 Eric Biggers [this message]
2020-03-14 20:50 ` [PATCH 1/4] fscrypt: add FS_IOC_GET_ENCRYPTION_NONCE ioctl Eric Biggers
2020-03-19 20:19 ` Theodore Y. Ts'o
2020-03-14 20:50 ` [PATCH 2/4] ext4: wire up FS_IOC_GET_ENCRYPTION_NONCE Eric Biggers
2020-03-19 20:19 ` Theodore Y. Ts'o
2020-03-14 20:50 ` [PATCH 3/4] f2fs: " Eric Biggers
2020-03-14 20:50 ` [PATCH 4/4] ubifs: " Eric Biggers
2020-03-19 17:49 ` [PATCH 0/4] fscrypt: add ioctl to get file's encryption nonce Eric Biggers
2020-03-22 3:30 ` Eric Biggers
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=20200314205052.93294-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-api@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-mtd@lists.infradead.org \
/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).