From: Eric Biggers <ebiggers@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
ceph-devel@vger.kernel.org, linux-btrfs@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 6.8
Date: Mon, 8 Jan 2024 14:48:11 -0800 [thread overview]
Message-ID: <20240108224811.GA94550@sol.localdomain> (raw)
The following changes since commit 33cc938e65a98f1d29d0a18403dbbee050dcad9a:
Linux 6.7-rc4 (2023-12-03 18:52:56 +0900)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus
for you to fetch changes up to 2a0e85719892a1d63f8f287563e2c1778a77879e:
fs: move fscrypt keyring destruction to after ->put_super (2023-12-27 21:56:01 -0600)
----------------------------------------------------------------
Adjust the timing of the fscrypt keyring destruction, to prepare for
btrfs's fscrypt support. Also document that CephFS supports fscrypt now.
----------------------------------------------------------------
Eric Biggers (4):
fscrypt.rst: update definition of struct fscrypt_context_v2
fscrypt: update comment for do_remove_key()
fscrypt: document that CephFS supports fscrypt now
f2fs: move release of block devices to after kill_block_super()
Josef Bacik (1):
fs: move fscrypt keyring destruction to after ->put_super
Documentation/filesystems/fscrypt.rst | 21 +++++++++++----------
fs/crypto/Kconfig | 2 +-
fs/crypto/keyring.c | 6 +++---
fs/f2fs/super.c | 13 ++++++++-----
fs/super.c | 12 ++++++------
5 files changed, 29 insertions(+), 25 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
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-fsdevel@vger.kernel.org,
Jaegeuk Kim <jaegeuk@kernel.org>,
ceph-devel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: [f2fs-dev] [GIT PULL] fscrypt updates for 6.8
Date: Mon, 8 Jan 2024 14:48:11 -0800 [thread overview]
Message-ID: <20240108224811.GA94550@sol.localdomain> (raw)
The following changes since commit 33cc938e65a98f1d29d0a18403dbbee050dcad9a:
Linux 6.7-rc4 (2023-12-03 18:52:56 +0900)
are available in the Git repository at:
https://git.kernel.org/pub/scm/fs/fscrypt/linux.git tags/fscrypt-for-linus
for you to fetch changes up to 2a0e85719892a1d63f8f287563e2c1778a77879e:
fs: move fscrypt keyring destruction to after ->put_super (2023-12-27 21:56:01 -0600)
----------------------------------------------------------------
Adjust the timing of the fscrypt keyring destruction, to prepare for
btrfs's fscrypt support. Also document that CephFS supports fscrypt now.
----------------------------------------------------------------
Eric Biggers (4):
fscrypt.rst: update definition of struct fscrypt_context_v2
fscrypt: update comment for do_remove_key()
fscrypt: document that CephFS supports fscrypt now
f2fs: move release of block devices to after kill_block_super()
Josef Bacik (1):
fs: move fscrypt keyring destruction to after ->put_super
Documentation/filesystems/fscrypt.rst | 21 +++++++++++----------
fs/crypto/Kconfig | 2 +-
fs/crypto/keyring.c | 6 +++---
fs/f2fs/super.c | 13 ++++++++-----
fs/super.c | 12 ++++++------
5 files changed, 29 insertions(+), 25 deletions(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2024-01-08 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 22:48 Eric Biggers [this message]
2024-01-08 22:48 ` [f2fs-dev] [GIT PULL] fscrypt updates for 6.8 Eric Biggers
2024-01-10 20:38 ` pr-tracker-bot
2024-01-10 20:38 ` [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=20240108224811.GA94550@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-btrfs@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-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 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.