linux-kernel - Re: [PATCH 5.4 000/658] 5.4.229-rc1 review

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Y8Zt42qAQ2BQdxL2@kroah.com>
Date:   Tue, 17 Jan 2023 10:44:03 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     stable@...r.kernel.org, patches@...ts.linux.dev,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
        akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
        lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
        f.fainelli@...il.com, sudipm.mukherjee@...il.com,
        srw@...dewatkins.net, rwarsow@....de
Subject: Re: [PATCH 5.4 000/658] 5.4.229-rc1 review

On Mon, Jan 16, 2023 at 12:20:25PM -0800, Guenter Roeck wrote:
> On Mon, Jan 16, 2023 at 04:41:28PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.4.229 release.
> > There are 658 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, 18 Jan 2023 15:47:28 +0000.
> > Anything received after that time might be too late.
> > 
> 
> Note: Exactly the same failures are seen in v4.19.269-522-gc75d2b5524ab,
> so I won't bother sending test results for that branch.
> 
> ---
> 
> Build results:
> 	total: 159 pass: 153 fail: 6
> Failed builds:
> 	i386:tools/perf
> 	riscv:defconfig
> 	s390:allnoconfig
> 	s390:tinyconfig
> 	um:defconfig
> 	x86_64:tools/perf
> Qemu test results:
> 	total: 449 pass: 413 fail: 36
> Failed tests:
> 	<all ppc64:pseries>
> 	<all riscv>
> 
> Details follow.
> 
> Guenter
> 
> ========
> 
> Building i386:tools/perf ... failed
> Building x86_64:tools/perf ... failed
> --------------
> Error log:
> util/debug.c: In function ‘perf_quiet_option’:
> util/debug.c:237:2: error: ‘debug_peo_args’ undeclared

Offending commit now dropped.

> Building riscv:defconfig ... failed
> --------------
> Error log:
> arch/riscv/kernel/stacktrace.c: In function 'walk_stackframe':
> arch/riscv/kernel/stacktrace.c:58:36: error: 'struct pt_regs' has no member named 'epc'

Patch dropped.

> 
> Building s390:allnoconfig ... failed
> Building s390:tinyconfig ... failed
> --------------
> Error log:
> s390-linux-ld: drivers/base/platform.o: in function `devm_platform_get_and_ioremap_resource':
> platform.c:(.text+0x594): undefined reference to `devm_ioremap_resource'
> s390-linux-ld: platform.c:(.text+0x5c2): undefined reference to `devm_ioremap_resource'
> 
> Building um:defconfig ... failed
> --------------
> Error log:
> ld: drivers/base/platform.o: in function `devm_platform_get_and_ioremap_resource':
> drivers/base/platform.c:82: undefined reference to `devm_ioremap_resource'

Same patches now dropped.

> 
> Runtime:
> 
> Building ppc64:pseries:pseries_defconfig:smp2:net,pcnet:initrd ... running ......R... failed (crashed)
> 
> BUG: Kernel NULL pointer dereference at 0x00000000
> Faulting instruction address: 0xc000000000046cc8
> Oops: Kernel access of bad area, sig: 11 [#1]
> BE SMP NR_CPUS=2048 NUMA pSeries
> Modules linked in:
> CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.19.270-rc1-00522-gc75d2b5524ab #1
> NIP:  c000000000046cc8 LR: c000000000046ca4 CTR: 0000000000000000
> REGS: c00000003e6878f0 TRAP: 0380   Not tainted  (4.19.270-rc1-00522-gc75d2b5524ab)
> MSR:  8000000002009032 <SF,VEC,EE,ME,IR,DR,RI>  CR: 84000882  XER: 00000000
> CFAR: c000000000162cf8 IRQMASK: 0
> GPR00: c000000000046ca4 c00000003e687b70 c000000001772000 0000000000000000
> GPR04: 0000000000000001 0000000000000001 c00000003e687990 00000000bc24d52c
> GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000003
> GPR12: 0000000024000882 c00000003ffff300 c000000000010e34 0000000000000000
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000000000 0000000000000000 c00000000125eea8 0000000000000001
> GPR24: c000000001379cd8 c000000001419f20 c0000000017b7d68 c0000000017b7d68
> GPR28: 0000000000000000 0000000000000002 c00000000160efe8 c00000000168ac60
> NIP [c000000000046cc8] .eeh_init+0x48/0x220
> LR [c000000000046ca4] .eeh_init+0x24/0x220
> Call Trace:
> [c00000003e687b70] [c000000000046ca4] .eeh_init+0x24/0x220 (unreliable)
> [c00000003e687c00] [c00000000001065c] .do_one_initcall+0x7c/0x430
> [c00000003e687ce0] [c000000001394db4] .kernel_init_freeable+0x538/0x62c
> [c00000003e687dc0] [c000000000010e4c] .kernel_init+0x18/0x14c
> [c00000003e687e30] [c00000000000c0d0] .ret_from_kernel_thread+0x58/0x68
> Instruction dump:
> 3c62ffd7 38631c10 4811c021 60000000 2c030000 408201c8 3d22000b e92904e0
> 2c290000 41820198 f8410028 e9290008 <e9490000> 7d4903a6 e8490008 4e800421
> ---[ end trace 8912d02d3e80c4ae ]---

This is odd, and I don't know how to track that down.  Any hints?

thanks,

greg k-h