lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025062530-friend-certainly-f8e4@gregkh>
Date: Wed, 25 Jun 2025 09:52:49 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jon Hunter <jonathanh@...dia.com>
Cc: patches@...ts.linux.dev, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux@...ck-us.net, shuah@...nel.org, patches@...nelci.org,
	lkft-triage@...ts.linaro.org, pavel@...x.de, f.fainelli@...il.com,
	sudipm.mukherjee@...il.com, srw@...dewatkins.net, rwarsow@....de,
	conor@...nel.org, hargar@...rosoft.com, broonie@...nel.org,
	linux-tegra@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 5.4 000/222] 5.4.295-rc1 review

On Wed, Jun 25, 2025 at 08:34:47AM +0100, Jon Hunter wrote:
> Hi Greg,
> 
> On 25/06/2025 08:16, Jon Hunter wrote:
> > On Mon, 23 Jun 2025 15:05:35 +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.4.295 release.
> > > There are 222 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 Wed, 25 Jun 2025 13:05:50 +0000.
> > > Anything received after that time might be too late.
> > > 
> > > The whole patch series can be found in one patch at:
> > > 	https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.295-rc1.gz
> > > or in the git tree and branch at:
> > > 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
> > > and the diffstat can be found below.
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > Failures detected for Tegra ...
> > 
> > Test results for stable-v5.4:
> >      10 builds:	7 pass, 3 fail
> >      18 boots:	18 pass, 0 fail
> >      39 tests:	39 pass, 0 fail
> > 
> > Linux version:	5.4.295-rc1-gca8c5417d1e6
> > Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
> >                  tegra194-p2972-0000, tegra20-ventana,
> >                  tegra210-p2371-2180, tegra210-p3450-0000,
> >                  tegra30-cardhu-a04
> > 
> > Builds failed:	arm+multi_v7
> 
> 
> I am seeing the following build error for ARM with the
> multi_v7_defconfig on our builders ...
> 
>   CC      drivers/firmware/qcom_scm-32.o
> /tmp/cc9gP1cd.s: Assembler messages:
> /tmp/cc9gP1cd.s:45: Error: selected processor does not support `smc #0' in ARM mode
> /tmp/cc9gP1cd.s:94: Error: selected processor does not support `smc #0' in ARM mode
> /tmp/cc9gP1cd.s:160: Error: selected processor does not support `smc #0' in ARM mode
> /tmp/cc9gP1cd.s:295: Error: selected processor does not support `smc #0' in ARM mode
> make[3]: *** [/home/jonathanh/nvidia/mlt-linux_next/kernel/scripts/Makefile.build:262: drivers/firmware/qcom_scm-32.o] Error 1
> 
> 
> Bisect is pointing to ...
> 
> # first bad commit: [0c23125c509b41be51f0d5acb843b079a098a40c] kbuild: Update assembler calls to use proper flags and language target
> 
> Reverting this fixes it but I also needed to revert the following due to dependencies ...
> 
> Nathan Chancellor <nathan@...nel.org>
>     kbuild: Add KBUILD_CPPFLAGS to as-option invocation
> 
> Nathan Chancellor <nathan@...nel.org>
>     kbuild: Add CLANG_FLAGS to as-instr

I've also dropped the others in this series and will push out a -rc2
soon, thanks for testing and letting me know.

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ