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-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Luis Henriques <lhenriques@suse.de>, Xiubo Li <xiubli@redhat.com>
Subject: [GIT PULL] fscrypt updates for 6.9
Date: Mon, 11 Mar 2024 21:17:29 -0700 [thread overview]
Message-ID: <20240312041729.GH1182@sol.localdomain> (raw)
The following changes since commit 41bccc98fb7931d63d03f326a746ac4d429c1dd3:
Linux 6.8-rc2 (2024-01-28 17:01:12 -0800)
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 8c62f31eddb71c6f6878258579318c1156045247:
fscrypt: shrink the size of struct fscrypt_inode_info slightly (2024-02-23 22:03:48 -0800)
----------------------------------------------------------------
Fix flakiness in a test by releasing the quota synchronously when a key
is removed, and other minor cleanups.
----------------------------------------------------------------
Eric Biggers (2):
fscrypt: write CBC-CTS instead of CTS-CBC
fscrypt: shrink the size of struct fscrypt_inode_info slightly
Luis Henriques (1):
fscrypt: clear keyring before calling key_put()
Xiubo Li (1):
fscrypt: explicitly require that inode->i_blkbits be set
Documentation/filesystems/fscrypt.rst | 27 +++++++++++++++------------
fs/crypto/fscrypt_private.h | 14 ++++++++------
fs/crypto/keyring.c | 8 ++++++--
fs/crypto/keysetup.c | 11 +++++++----
4 files changed, 36 insertions(+), 24 deletions(-)
next reply other threads:[~2024-03-12 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 4:17 Eric Biggers [this message]
2024-03-12 22:24 ` [GIT PULL] fscrypt updates for 6.9 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=20240312041729.GH1182@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lhenriques@suse.de \
--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 \
--cc=xiubli@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).