From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, dianders@google.com,
briannorris@google.com, momohatt@google.com,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 5.15 000/476] 5.15.149-rc1 review
Date: Thu, 25 Apr 2024 15:46:18 -0700 [thread overview]
Message-ID: <aceda6e2-cefb-4146-aef8-ff4bafa56e56@roeck-us.net> (raw)
In-Reply-To: <20240221130007.738356493@linuxfoundation.org>
Hi,
On 2/21/24 05:00, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.15.149 release.
> There are 476 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 23 Feb 2024 12:59:02 +0000.
> Anything received after that time might be too late.
>
[ ... ]
> Herbert Xu <herbert@gondor.apana.org.au>
> crypto: api - Disallow identical driver names
>
This patch results in a severe performance regression on arm64 systems;
there is more than 50% throughput loss on some sequential read tests.
The problem affects v5.15.y and older kernel branches.
Analysis shows that v5.15.y and older kernel _do_ try to register the same
crypto algorithm twice, once through
__crypto_register_alg
crypto_register_alg
crypto_register_skciphers
aes_init
and then again through
__crypto_register_alg
crypto_register_alg
crypto_register_skcipher
simd_skcipher_create_compat
aes_init
After above patch was applied, the second registration fails, resulting
in the regression.
The problem is not seen in later kernels due to commit 676e508122d9
("crypto: arm64/aes-ce - stop using SIMD helper for skciphers"). Applying this
commit or reverting above commit fixes the regression in v5.15.y and older.
Thanks is due to Momoko Hattori for reporting the problem and finding the
offending patch, Doug Anderson for finding the duplicate registration attempt,
and Brian Norris for finding the fix. I copied them on this e-mail in case
there are further questions.
Thanks,
Guenter
next prev parent reply other threads:[~2024-04-25 22:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 13:00 Greg Kroah-Hartman
2024-02-21 19:48 ` Jon Hunter
2024-02-21 23:43 ` Shuah Khan
2024-02-21 23:58 ` Florian Fainelli
2024-02-22 9:06 ` Shreeya Patel
2024-02-22 11:49 ` Naresh Kamboju
2024-02-22 19:22 ` Harshit Mogalapalli
2024-02-22 20:27 ` Allen
2024-02-22 23:13 ` Ron Economos
2024-02-23 1:24 ` Kelsey Steele
2024-04-25 22:46 ` Guenter Roeck [this message]
2024-04-26 8:44 ` Greg Kroah-Hartman
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=aceda6e2-cefb-4146-aef8-ff4bafa56e56@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=briannorris@google.com \
--cc=conor@kernel.org \
--cc=dianders@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=momohatt@google.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®