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-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [GIT PULL] fscrypt fix for v6.3-rc4
Date: Mon, 20 Mar 2023 13:56:17 -0700 [thread overview]
Message-ID: <20230320205617.GA1434@sol.localdomain> (raw)
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -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 4bcf6f827a79c59806c695dc280e763c5b6a6813:
fscrypt: check for NULL keyring in fscrypt_put_master_key_activeref() (2023-03-18 21:08:03 -0700)
----------------------------------------------------------------
Fix a bug where when a filesystem was being unmounted, the fscrypt
keyring was destroyed before inodes have been released by the Landlock
LSM. This bug was found by syzbot.
----------------------------------------------------------------
Eric Biggers (3):
fscrypt: destroy keyring after security_sb_delete()
fscrypt: improve fscrypt_destroy_keyring() documentation
fscrypt: check for NULL keyring in fscrypt_put_master_key_activeref()
fs/crypto/keyring.c | 23 +++++++++++++----------
fs/super.c | 15 ++++++++++++---
2 files changed, 25 insertions(+), 13 deletions(-)
next reply other threads:[~2023-03-20 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 20:56 Eric Biggers [this message]
2023-03-20 22:16 ` [GIT PULL] fscrypt fix for v6.3-rc4 Linus Torvalds
2023-03-20 22:59 ` Eric Biggers
2023-03-21 2:03 ` Theodore Ts'o
2023-03-21 19:03 ` Linus Torvalds
2023-03-20 22:40 ` 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=20230320205617.GA1434@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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.