From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org
Subject: [PATCH 6.0 0/2] fscrypt fixes for stable
Date: Fri, 4 Nov 2022 15:54:37 -0700 [thread overview]
Message-ID: <20221104225439.338239-1-ebiggers@kernel.org> (raw)
Please apply these to 6.0-stable.
Eric Biggers (2):
fscrypt: stop using keyrings subsystem for fscrypt_master_key
fscrypt: fix keyring memory leak on mount failure
fs/crypto/fscrypt_private.h | 71 ++++--
fs/crypto/hooks.c | 10 +-
fs/crypto/keyring.c | 491 +++++++++++++++++++-----------------
fs/crypto/keysetup.c | 81 +++---
fs/crypto/policy.c | 8 +-
fs/super.c | 3 +-
include/linux/fs.h | 2 +-
include/linux/fscrypt.h | 4 +-
8 files changed, 359 insertions(+), 311 deletions(-)
base-commit: 3a2fa3c01fc7c2183eb3278bd912e5bcec20eb2a
--
2.38.1
next reply other threads:[~2022-11-04 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 22:54 Eric Biggers [this message]
2022-11-04 22:54 ` [PATCH 6.0 1/2] fscrypt: stop using keyrings subsystem for fscrypt_master_key Eric Biggers
2022-11-04 22:54 ` [PATCH 6.0 2/2] fscrypt: fix keyring memory leak on mount failure Eric Biggers
2022-11-07 8:59 ` [PATCH 6.0 0/2] 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=20221104225439.338239-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).