Received-SPF: pass (google.com: domain of linux-kernel+bounces-159724-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Fri, 26 Apr 2024 10:44:18 +0200
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org, 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
Message-ID: <2024042603-sleek-janitor-34f8@gregkh>
References: <20240221130007.738356493@linuxfoundation.org>
 <aceda6e2-cefb-4146-aef8-ff4bafa56e56@roeck-us.net>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aceda6e2-cefb-4146-aef8-ff4bafa56e56@roeck-us.net>

On Thu, Apr 25, 2024 at 03:46:18PM -0700, Guenter Roeck wrote:
> 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 for the report.  I got a report that this breaks some android
systems as well due to some FIPS crypto code that happens to duplicate
the names as well.  I think reverting it makes sense and I'll queue that
up for the next round of releases.

greg k-h