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>,
Satya Tangirala <satyat@google.com>
Subject: [GIT PULL] fscrypt updates for 5.9
Date: Mon, 3 Aug 2020 00:05:47 -0700 [thread overview]
Message-ID: <20200803070547.GA24480@sol.localdomain> (raw)
The following changes since commit dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258:
Linux 5.8-rc4 (2020-07-05 16:20:22 -0700)
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 55e32c54bbd5741cad462c9ee00c453c72fa74b9:
fscrypt: don't load ->i_crypt_info before it's known to be valid (2020-07-30 14:21:50 -0700)
----------------------------------------------------------------
This release, we add support for inline encryption via the blk-crypto
framework which was added in 5.8. Now when an ext4 or f2fs filesystem
is mounted with '-o inlinecrypt', the contents of encrypted files will
be encrypted/decrypted via blk-crypto, instead of directly using the
crypto API. This model allows taking advantage of the inline encryption
hardware that is integrated into the UFS or eMMC host controllers on
most mobile SoCs. Note that this is just an alternate implementation;
the ciphertext written to disk stays the same.
(This pull request does *not* include support for direct I/O on
encrypted files, which blk-crypto makes possible, since that part is
still being discussed.)
Besides the above feature update, there are also a few fixes and
cleanups, e.g. strengthening some memory barriers that may be too weak.
All these patches have been in linux-next with no reported issues. I've
also tested them with the fscrypt xfstests, as usual. It's also been
tested that the inline encryption support works with the support for
Qualcomm and Mediatek inline encryption hardware that will be in the
scsi pull request for 5.9. Also, several SoC vendors are already using
a previous, functionally equivalent version of these patches.
----------------------------------------------------------------
Eric Biggers (9):
ext4: add inline encryption support
fscrypt: add comments that describe the HKDF info strings
fscrypt: rename FS_KEY_DERIVATION_NONCE_SIZE
fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
fscrypt: switch fscrypt_do_sha256() to use the SHA-256 library
fscrypt: use smp_load_acquire() for fscrypt_prepared_key
fscrypt: use smp_load_acquire() for ->s_master_keys
fscrypt: use smp_load_acquire() for ->i_crypt_info
fscrypt: don't load ->i_crypt_info before it's known to be valid
Satya Tangirala (4):
fs: introduce SB_INLINECRYPT
fscrypt: add inline encryption support
f2fs: add inline encryption support
fscrypt: document inline encryption support
Documentation/admin-guide/ext4.rst | 7 +
Documentation/filesystems/f2fs.rst | 7 +
Documentation/filesystems/fscrypt.rst | 25 ++-
fs/buffer.c | 7 +-
fs/crypto/Kconfig | 8 +-
fs/crypto/Makefile | 1 +
fs/crypto/bio.c | 51 +++++
fs/crypto/crypto.c | 4 +-
fs/crypto/fname.c | 45 ++---
fs/crypto/fscrypt_private.h | 144 ++++++++++---
fs/crypto/inline_crypt.c | 367 ++++++++++++++++++++++++++++++++++
fs/crypto/keyring.c | 21 +-
fs/crypto/keysetup.c | 91 ++++++---
fs/crypto/keysetup_v1.c | 20 +-
fs/crypto/policy.c | 20 +-
fs/ext4/inode.c | 4 +-
fs/ext4/page-io.c | 6 +-
fs/ext4/readpage.c | 11 +-
fs/ext4/super.c | 12 ++
fs/f2fs/compress.c | 2 +-
fs/f2fs/data.c | 79 ++++++--
fs/f2fs/super.c | 35 ++++
include/linux/fs.h | 1 +
include/linux/fscrypt.h | 111 +++++++++-
24 files changed, 940 insertions(+), 139 deletions(-)
create mode 100644 fs/crypto/inline_crypt.c
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Satya Tangirala <satyat@google.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: [f2fs-dev] [GIT PULL] fscrypt updates for 5.9
Date: Mon, 3 Aug 2020 00:05:47 -0700 [thread overview]
Message-ID: <20200803070547.GA24480@sol.localdomain> (raw)
The following changes since commit dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258:
Linux 5.8-rc4 (2020-07-05 16:20:22 -0700)
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 55e32c54bbd5741cad462c9ee00c453c72fa74b9:
fscrypt: don't load ->i_crypt_info before it's known to be valid (2020-07-30 14:21:50 -0700)
----------------------------------------------------------------
This release, we add support for inline encryption via the blk-crypto
framework which was added in 5.8. Now when an ext4 or f2fs filesystem
is mounted with '-o inlinecrypt', the contents of encrypted files will
be encrypted/decrypted via blk-crypto, instead of directly using the
crypto API. This model allows taking advantage of the inline encryption
hardware that is integrated into the UFS or eMMC host controllers on
most mobile SoCs. Note that this is just an alternate implementation;
the ciphertext written to disk stays the same.
(This pull request does *not* include support for direct I/O on
encrypted files, which blk-crypto makes possible, since that part is
still being discussed.)
Besides the above feature update, there are also a few fixes and
cleanups, e.g. strengthening some memory barriers that may be too weak.
All these patches have been in linux-next with no reported issues. I've
also tested them with the fscrypt xfstests, as usual. It's also been
tested that the inline encryption support works with the support for
Qualcomm and Mediatek inline encryption hardware that will be in the
scsi pull request for 5.9. Also, several SoC vendors are already using
a previous, functionally equivalent version of these patches.
----------------------------------------------------------------
Eric Biggers (9):
ext4: add inline encryption support
fscrypt: add comments that describe the HKDF info strings
fscrypt: rename FS_KEY_DERIVATION_NONCE_SIZE
fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
fscrypt: switch fscrypt_do_sha256() to use the SHA-256 library
fscrypt: use smp_load_acquire() for fscrypt_prepared_key
fscrypt: use smp_load_acquire() for ->s_master_keys
fscrypt: use smp_load_acquire() for ->i_crypt_info
fscrypt: don't load ->i_crypt_info before it's known to be valid
Satya Tangirala (4):
fs: introduce SB_INLINECRYPT
fscrypt: add inline encryption support
f2fs: add inline encryption support
fscrypt: document inline encryption support
Documentation/admin-guide/ext4.rst | 7 +
Documentation/filesystems/f2fs.rst | 7 +
Documentation/filesystems/fscrypt.rst | 25 ++-
fs/buffer.c | 7 +-
fs/crypto/Kconfig | 8 +-
fs/crypto/Makefile | 1 +
fs/crypto/bio.c | 51 +++++
fs/crypto/crypto.c | 4 +-
fs/crypto/fname.c | 45 ++---
fs/crypto/fscrypt_private.h | 144 ++++++++++---
fs/crypto/inline_crypt.c | 367 ++++++++++++++++++++++++++++++++++
fs/crypto/keyring.c | 21 +-
fs/crypto/keysetup.c | 91 ++++++---
fs/crypto/keysetup_v1.c | 20 +-
fs/crypto/policy.c | 20 +-
fs/ext4/inode.c | 4 +-
fs/ext4/page-io.c | 6 +-
fs/ext4/readpage.c | 11 +-
fs/ext4/super.c | 12 ++
fs/f2fs/compress.c | 2 +-
fs/f2fs/data.c | 79 ++++++--
fs/f2fs/super.c | 35 ++++
include/linux/fs.h | 1 +
include/linux/fscrypt.h | 111 +++++++++-
24 files changed, 940 insertions(+), 139 deletions(-)
create mode 100644 fs/crypto/inline_crypt.c
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Satya Tangirala <satyat@google.com>,
Theodore Ts'o <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: [GIT PULL] fscrypt updates for 5.9
Date: Mon, 3 Aug 2020 00:05:47 -0700 [thread overview]
Message-ID: <20200803070547.GA24480@sol.localdomain> (raw)
The following changes since commit dcb7fd82c75ee2d6e6f9d8cc71c52519ed52e258:
Linux 5.8-rc4 (2020-07-05 16:20:22 -0700)
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 55e32c54bbd5741cad462c9ee00c453c72fa74b9:
fscrypt: don't load ->i_crypt_info before it's known to be valid (2020-07-30 14:21:50 -0700)
----------------------------------------------------------------
This release, we add support for inline encryption via the blk-crypto
framework which was added in 5.8. Now when an ext4 or f2fs filesystem
is mounted with '-o inlinecrypt', the contents of encrypted files will
be encrypted/decrypted via blk-crypto, instead of directly using the
crypto API. This model allows taking advantage of the inline encryption
hardware that is integrated into the UFS or eMMC host controllers on
most mobile SoCs. Note that this is just an alternate implementation;
the ciphertext written to disk stays the same.
(This pull request does *not* include support for direct I/O on
encrypted files, which blk-crypto makes possible, since that part is
still being discussed.)
Besides the above feature update, there are also a few fixes and
cleanups, e.g. strengthening some memory barriers that may be too weak.
All these patches have been in linux-next with no reported issues. I've
also tested them with the fscrypt xfstests, as usual. It's also been
tested that the inline encryption support works with the support for
Qualcomm and Mediatek inline encryption hardware that will be in the
scsi pull request for 5.9. Also, several SoC vendors are already using
a previous, functionally equivalent version of these patches.
----------------------------------------------------------------
Eric Biggers (9):
ext4: add inline encryption support
fscrypt: add comments that describe the HKDF info strings
fscrypt: rename FS_KEY_DERIVATION_NONCE_SIZE
fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
fscrypt: switch fscrypt_do_sha256() to use the SHA-256 library
fscrypt: use smp_load_acquire() for fscrypt_prepared_key
fscrypt: use smp_load_acquire() for ->s_master_keys
fscrypt: use smp_load_acquire() for ->i_crypt_info
fscrypt: don't load ->i_crypt_info before it's known to be valid
Satya Tangirala (4):
fs: introduce SB_INLINECRYPT
fscrypt: add inline encryption support
f2fs: add inline encryption support
fscrypt: document inline encryption support
Documentation/admin-guide/ext4.rst | 7 +
Documentation/filesystems/f2fs.rst | 7 +
Documentation/filesystems/fscrypt.rst | 25 ++-
fs/buffer.c | 7 +-
fs/crypto/Kconfig | 8 +-
fs/crypto/Makefile | 1 +
fs/crypto/bio.c | 51 +++++
fs/crypto/crypto.c | 4 +-
fs/crypto/fname.c | 45 ++---
fs/crypto/fscrypt_private.h | 144 ++++++++++---
fs/crypto/inline_crypt.c | 367 ++++++++++++++++++++++++++++++++++
fs/crypto/keyring.c | 21 +-
fs/crypto/keysetup.c | 91 ++++++---
fs/crypto/keysetup_v1.c | 20 +-
fs/crypto/policy.c | 20 +-
fs/ext4/inode.c | 4 +-
fs/ext4/page-io.c | 6 +-
fs/ext4/readpage.c | 11 +-
fs/ext4/super.c | 12 ++
fs/f2fs/compress.c | 2 +-
fs/f2fs/data.c | 79 ++++++--
fs/f2fs/super.c | 35 ++++
include/linux/fs.h | 1 +
include/linux/fscrypt.h | 111 +++++++++-
24 files changed, 940 insertions(+), 139 deletions(-)
create mode 100644 fs/crypto/inline_crypt.c
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-08-03 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 7:05 Eric Biggers [this message]
2020-08-03 7:05 ` [GIT PULL] fscrypt updates for 5.9 Eric Biggers
2020-08-03 7:05 ` [f2fs-dev] " Eric Biggers
2020-08-03 17:55 ` pr-tracker-bot
2020-08-03 17:55 ` pr-tracker-bot
2020-08-03 17:55 ` [f2fs-dev] " 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=20200803070547.GA24480@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=satyat@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.