From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH 5.10 0/3] fscrypt fixes for stable
Date: Fri, 4 Nov 2022 16:37:57 -0700 [thread overview]
Message-ID: <20221104233800.421135-1-ebiggers@kernel.org> (raw)
Please apply these to 5.10-stable.
Eric Biggers (3):
fscrypt: simplify master key locking
fscrypt: stop using keyrings subsystem for fscrypt_master_key
fscrypt: fix keyring memory leak on mount failure
fs/crypto/fscrypt_private.h | 80 ++++--
fs/crypto/hooks.c | 8 +-
fs/crypto/keyring.c | 495 +++++++++++++++++++-----------------
fs/crypto/keysetup.c | 85 +++----
fs/crypto/policy.c | 8 +-
fs/super.c | 3 +-
include/linux/fs.h | 2 +-
include/linux/fscrypt.h | 4 +-
8 files changed, 360 insertions(+), 325 deletions(-)
base-commit: 95aa34f72132ee42ee3f632a5540c84a5ee8624f
--
2.38.1
next reply other threads:[~2022-11-04 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 23:37 Eric Biggers [this message]
2022-11-04 23:37 ` [PATCH 5.10 1/3] fscrypt: simplify master key locking Eric Biggers
2022-11-04 23:37 ` [PATCH 5.10 2/3] fscrypt: stop using keyrings subsystem for fscrypt_master_key Eric Biggers
2022-11-04 23:38 ` [PATCH 5.10 3/3] fscrypt: fix keyring memory leak on mount failure Eric Biggers
2022-11-07 9:07 ` [PATCH 5.10 0/3] fscrypt fixes for stable Greg KH
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=20221104233800.421135-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).