From: Herbert Xu <herbert@gondor.apana.org.au>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Taeyang Lee <0wn@theori.io>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Eric Biggers <ebiggers@kernel.org>,
Linus Torvalds <torvalds@linuxfoundation.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Greg KH <gregkh@linuxfoundation.org>,
davem@davemloft.net, Brian Pak <bpak@theori.io>,
Juno Im <juno@theori.io>, Jungwon Lim <setuid0@theori.io>,
douzzer@mega.nu,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH] crypto: algif_aead - Revert to operating out-of-place
Date: Fri, 10 Apr 2026 22:52:32 +0800 [thread overview]
Message-ID: <adkOsK-uPRsv49Yz@gondor.apana.org.au> (raw)
In-Reply-To: <73ab5267-57b8-4394-9c10-4ee3bf92e444@leemhuis.info>
On Thu, Apr 09, 2026 at 05:24:49PM +0200, Thorsten Leemhuis wrote:
>
> This meanwhile became a664bf3d603dc3 ("crypto: algif_aead - Revert to
> operating out-of-place") [v7.0-rc7] and according to Daniel Pouzzner
> causes a regression reported here:
> https://bugzilla.kernel.org/show_bug.cgi?id=221332
>
> To quote: """Seeing Oopses and some kernel panics in 7.0_rc7 under
> modest load, roughly 10% of test runs. Discovered by serendipity
> running libkcapi test.sh to test our own crypto module (libwolfssl.ko),
> then reproduced on native crypto to exclude us as the cause.
Please try these patches which are in the queue:
https://patchwork.kernel.org/project/linux-crypto/patch/adCAFOgQ0y_I7SC7@gondor.apana.org.au/
https://patchwork.kernel.org/project/linux-crypto/patch/adBbht8ERe0z-z3B@gondor.apana.org.au/
Both fix pre-existing bugs that were uncovered by the aformentioned
change and syzbot.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2026-04-10 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:21 [PATCH] crypto: authencesn - Copy high sequence number from src after out-of-place decryption Herbert Xu
2026-03-25 16:23 ` Linus Torvalds
2026-03-26 4:17 ` Herbert Xu
2026-03-26 6:45 ` Herbert Xu
2026-03-26 6:46 ` [PATCH] crypto: authencesn - Use memcpy_from/to_sglist Herbert Xu
2026-05-02 4:53 ` [v2 PATCH] " Herbert Xu
2026-03-25 17:59 ` [PATCH] crypto: authencesn - Copy high sequence number from src after out-of-place decryption Taeyang Lee
2026-03-26 6:30 ` [PATCH] crypto: algif_aead - Revert to operating out-of-place Herbert Xu
2026-03-26 17:43 ` Taeyang Lee
2026-04-03 4:49 ` Taeyang Lee
2026-04-03 5:15 ` Taeyang Lee
2026-04-09 15:24 ` Thorsten Leemhuis
2026-04-10 14:52 ` Herbert Xu [this message]
2026-04-10 15:33 ` Daniel Pouzzner
2026-04-12 5:32 ` [v2 PATCH] crypto: algif_aead - Fix minimum RX size check for decryption Herbert Xu
2026-04-13 18:46 ` Daniel Pouzzner
2026-03-27 6:04 ` [v2 PATCH] crypto: authencesn - Do not place hiseq at end of dst for out-of-place decryption Herbert Xu
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=adkOsK-uPRsv49Yz@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=0wn@theori.io \
--cc=bpak@theori.io \
--cc=davem@davemloft.net \
--cc=douzzer@mega.nu \
--cc=ebiggers@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=juno@theori.io \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=setuid0@theori.io \
--cc=torvalds@linuxfoundation.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