From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fscrypt: Use lock guards for mutexes
Date: Sun, 5 Jul 2026 12:11:07 -0700 [thread overview]
Message-ID: <20260705191107.GA41916@quark> (raw)
In-Reply-To: <20260618184852.3469301-1-ebiggers@kernel.org>
On Thu, Jun 18, 2026 at 06:48:52PM +0000, Eric Biggers wrote:
> Replace all remaining calls to mutex_lock() and mutex_unlock() in
> fs/crypto/ with lock guards. No functional change.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This is intended to be taken through the fscrypt tree for 7.3
>
> fs/crypto/crypto.c | 13 ++++---------
> fs/crypto/keyring.c | 3 +--
> fs/crypto/keysetup.c | 23 +++++++++++------------
> 3 files changed, 16 insertions(+), 23 deletions(-)
Applied to https://git.kernel.org/pub/scm/fs/fscrypt/linux.git/log/?h=for-next
- Eric
prev parent reply other threads:[~2026-07-05 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 18:48 [PATCH] fscrypt: Use lock guards for mutexes Eric Biggers
2026-07-05 19:11 ` 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=20260705191107.GA41916@quark \
--to=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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