From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Subject: Re: [PATCH] fscrypt: Explicitly zeroize sw_secret in error path
Date: Sat, 24 Oct 2026 11:03:56 -0700 [thread overview]
Message-ID: <20261024180356.GA2553@quark> (raw)
In-Reply-To: <20261021224431.2353673-1-ebiggers@kernel.org>
On Wed, Oct 21, 2026 at 10:44:31PM +0000, Eric Biggers wrote:
> Explicitly zeroize the sw_secret array in the case where
> fscrypt_derive_sw_secret() fails, in case anything was written to it.
> Doesn't really matter, but this came up in a code review.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> fs/crypto/keyring.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Applied to https://git.kernel.org/pub/scm/fs/fscrypt/linux.git/log/?h=for-next
- Eric
prev parent reply other threads:[~2026-10-24 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 22:44 [PATCH] fscrypt: Explicitly zeroize sw_secret in error path Eric Biggers
2026-10-24 18:03 ` Eric Biggers [this message]
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=20261024180356.GA2553@quark \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@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 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.