Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 6.12.y 4/4] crypto: x86/aegis - Fix sleeping when disallowed on PREEMPT_RT
Date: Thu, 21 Aug 2025 23:28:56 -0400	[thread overview]
Message-ID: <aKfj-C27OQBWNEMq@laps> (raw)
In-Reply-To: <20250822032304.GA80178@quark>

On Thu, Aug 21, 2025 at 11:23:04PM -0400, Eric Biggers wrote:
>On Thu, Aug 21, 2025 at 11:06:17PM -0400, Sasha Levin wrote:
>> From: Eric Biggers <ebiggers@kernel.org>
>>
>> [ Upstream commit c7f49dadfcdf27e1f747442e874e9baa52ab7674 ]
>>
>> skcipher_walk_done() can call kfree(), which takes a spinlock, which
>> makes it incorrect to call while preemption is disabled on PREEMPT_RT.
>> Therefore, end the kernel-mode FPU section before calling
>> skcipher_walk_done(), and restart it afterwards.
>>
>> Moreover, pass atomic=false to skcipher_walk_aead_encrypt() instead of
>> atomic=true.  The point of atomic=true was to make skcipher_walk_done()
>> safe to call while in a kernel-mode FPU section, but that does not
>> actually work.  So just use the usual atomic=false.
>>
>> Fixes: 1d373d4e8e15 ("crypto: x86 - Add optimized AEGIS implementations")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
>> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>>  arch/x86/crypto/aegis128-aesni-glue.c | 8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>
>1. Missing Cc of the relevant mailing lists
>2. Missing cover letter

This was sent following the instructions in the FAILED: email generated by
Greg. If you feel its insufficient, take it up with him.

>3. Missing base-commit, and doesn't apply to stable/linux-6.16.y

As the subject line indicates, this applies on 6.12, not 6.16.

>4. Two different series were sent out, both containing this patch

You might have missed that they're for different trees?

>No reason to even take a look at the patch content until it's in a
>reviewable state.

Sure, appologies, please ignore the series.

-- 
Thanks,
Sasha

  reply	other threads:[~2025-08-22  3:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 12:55 FAILED: patch "[PATCH] crypto: x86/aegis - Fix sleeping when disallowed on" failed to apply to 6.12-stable tree gregkh
2025-08-22  3:06 ` [PATCH 6.12.y 1/4] crypto: x86/aegis128 - eliminate some indirect calls Sasha Levin
2025-08-22  3:06   ` [PATCH 6.12.y 2/4] crypto: x86/aegis128 - optimize length block preparation using SSE4.1 Sasha Levin
2025-08-22  3:06   ` [PATCH 6.12.y 3/4] crypto: x86/aegis128 - improve assembly function prototypes Sasha Levin
2025-08-22  3:06   ` [PATCH 6.12.y 4/4] crypto: x86/aegis - Fix sleeping when disallowed on PREEMPT_RT Sasha Levin
2025-08-22  3:23     ` Eric Biggers
2025-08-22  3:28       ` Sasha Levin [this message]
2025-08-22  3:39         ` Eric Biggers
2025-08-22  3:48           ` Eric Biggers
2025-08-22  3:56           ` Sasha Levin
2025-08-22  4:10             ` Eric Biggers

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=aKfj-C27OQBWNEMq@laps \
    --to=sashal@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --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