All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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.19
Date: Mon, 23 May 2022 00:07:51 -0700	[thread overview]
Message-ID: <Yosyx2FYZOIOWs9g@sol.localdomain> (raw)

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

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 218d921b581eadf312c8ef0e09113b111f104eeb:

  fscrypt: add new helper functions for test_dummy_encryption (2022-05-09 16:18:54 -0700)

----------------------------------------------------------------

Some cleanups for fs/crypto/:

- Split up the misleadingly-named FS_CRYPTO_BLOCK_SIZE constant.

- Consistently report the encryption implementation that is being used.

- Add helper functions for the test_dummy_encryption mount option that
  work properly with the new mount API.  ext4 and f2fs will use these.

----------------------------------------------------------------
Eric Biggers (4):
      fscrypt: split up FS_CRYPTO_BLOCK_SIZE
      fscrypt: log when starting to use inline encryption
      fscrypt: factor out fscrypt_policy_to_key_spec()
      fscrypt: add new helper functions for test_dummy_encryption

 fs/crypto/crypto.c          |  10 ++--
 fs/crypto/fname.c           |  11 +++-
 fs/crypto/fscrypt_private.h |  10 +++-
 fs/crypto/inline_crypt.c    |  33 ++++++++++-
 fs/crypto/keyring.c         |  64 +++++++++++++++++----
 fs/crypto/keysetup.c        |  22 ++------
 fs/crypto/policy.c          | 132 ++++++++++++++++++++++++++------------------
 fs/ubifs/ubifs.h            |   2 +-
 include/linux/fscrypt.h     |  51 ++++++++++++++++-
 9 files changed, 238 insertions(+), 97 deletions(-)


_______________________________________________
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: 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.19
Date: Mon, 23 May 2022 00:07:51 -0700	[thread overview]
Message-ID: <Yosyx2FYZOIOWs9g@sol.localdomain> (raw)

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

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 218d921b581eadf312c8ef0e09113b111f104eeb:

  fscrypt: add new helper functions for test_dummy_encryption (2022-05-09 16:18:54 -0700)

----------------------------------------------------------------

Some cleanups for fs/crypto/:

- Split up the misleadingly-named FS_CRYPTO_BLOCK_SIZE constant.

- Consistently report the encryption implementation that is being used.

- Add helper functions for the test_dummy_encryption mount option that
  work properly with the new mount API.  ext4 and f2fs will use these.

----------------------------------------------------------------
Eric Biggers (4):
      fscrypt: split up FS_CRYPTO_BLOCK_SIZE
      fscrypt: log when starting to use inline encryption
      fscrypt: factor out fscrypt_policy_to_key_spec()
      fscrypt: add new helper functions for test_dummy_encryption

 fs/crypto/crypto.c          |  10 ++--
 fs/crypto/fname.c           |  11 +++-
 fs/crypto/fscrypt_private.h |  10 +++-
 fs/crypto/inline_crypt.c    |  33 ++++++++++-
 fs/crypto/keyring.c         |  64 +++++++++++++++++----
 fs/crypto/keysetup.c        |  22 ++------
 fs/crypto/policy.c          | 132 ++++++++++++++++++++++++++------------------
 fs/ubifs/ubifs.h            |   2 +-
 include/linux/fscrypt.h     |  51 ++++++++++++++++-
 9 files changed, 238 insertions(+), 97 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
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.19
Date: Mon, 23 May 2022 00:07:51 -0700	[thread overview]
Message-ID: <Yosyx2FYZOIOWs9g@sol.localdomain> (raw)

The following changes since commit ce522ba9ef7e2d9fb22a39eb3371c0c64e2a433e:

  Linux 5.18-rc2 (2022-04-10 14:21:36 -1000)

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 218d921b581eadf312c8ef0e09113b111f104eeb:

  fscrypt: add new helper functions for test_dummy_encryption (2022-05-09 16:18:54 -0700)

----------------------------------------------------------------

Some cleanups for fs/crypto/:

- Split up the misleadingly-named FS_CRYPTO_BLOCK_SIZE constant.

- Consistently report the encryption implementation that is being used.

- Add helper functions for the test_dummy_encryption mount option that
  work properly with the new mount API.  ext4 and f2fs will use these.

----------------------------------------------------------------
Eric Biggers (4):
      fscrypt: split up FS_CRYPTO_BLOCK_SIZE
      fscrypt: log when starting to use inline encryption
      fscrypt: factor out fscrypt_policy_to_key_spec()
      fscrypt: add new helper functions for test_dummy_encryption

 fs/crypto/crypto.c          |  10 ++--
 fs/crypto/fname.c           |  11 +++-
 fs/crypto/fscrypt_private.h |  10 +++-
 fs/crypto/inline_crypt.c    |  33 ++++++++++-
 fs/crypto/keyring.c         |  64 +++++++++++++++++----
 fs/crypto/keysetup.c        |  22 ++------
 fs/crypto/policy.c          | 132 ++++++++++++++++++++++++++------------------
 fs/ubifs/ubifs.h            |   2 +-
 include/linux/fscrypt.h     |  51 ++++++++++++++++-
 9 files changed, 238 insertions(+), 97 deletions(-)

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

             reply	other threads:[~2022-05-23  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  7:07 Eric Biggers [this message]
2022-05-23  7:07 ` [GIT PULL] fscrypt updates for 5.19 Eric Biggers
2022-05-23  7:07 ` Eric Biggers
2022-05-24 19:53 ` pr-tracker-bot
2022-05-24 19:53   ` pr-tracker-bot
2022-05-24 19:53   ` [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=Yosyx2FYZOIOWs9g@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 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.