stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King |
Bug Description
During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops.
16:20:34 DEBUG| [stdout] sysinfo STARTING
16:20:39 DEBUG| [stdout] sysinfo RETURNED 0
16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed)
16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c0000000c25ffce0) - exploit attempt? (uid: 0)
16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch
16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc0000000c25ffce0
16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1]
16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_
16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk]
16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu
16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c0000000c25ffce0 LR: c00000000063f058 CTR: c0000000c25ffce0
16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c000000109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic)
16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 8000000010009033 <SF,EE,
16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c00000000063f054 IRQMASK: 0
16:20:39 DEBUG| [stdout] GPR00: c00000000063f034 c000000109703aa0 c000000001a4bb00 c00000007cef3000
16:20:39 DEBUG| [stdout] GPR04: c0000000c25ffc18 0000000000000000 0000000000000000 0000000000000000
16:20:39 DEBUG| [stdout] GPR08: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
16:20:39 DEBUG| [stdout] GPR12: c0000000c25ffce0 c00000003fffee00 000079b6987b4410 0000000000000000
16:20:39 DEBUG| [stdout] GPR16: 000079b698b30000 000079b6987b0320 000079b69771f240 000079b6987b4420
16:20:39 DEBUG| [stdout] GPR20: 0000000000000000 0000000000000000 000079b6880010a0 000079b698a4d3a0
16:20:39 DEBUG| [stdout] GPR24: c000000109d56cc0 c0000001fde0cd8c c0000000c25ffce0 c000000109d56ca0
16:20:39 DEBUG| [stdout] GPR28: c000000109d56cc0 0000000000000000 c00000007cef3000 c000000109d56c90
16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c0000000c25ffce0] 0xc0000000c25ffce0
16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c00000000063f058] fuse_request_
16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace:
16:20:39 DEBUG| [stdout] [ 6521.210448] [c000000109703aa0] [c00000000063f034] fuse_request_
16:20:39 DEBUG| [stdout] [ 6521.210520] [c000000109703af0] [c000000000642ebc] fuse_dev_
16:20:39 DEBUG| [stdout] [ 6521.210591] [c000000109703b70] [c000000000643654] fuse_dev_
16:20:39 DEBUG| [stdout] [ 6521.210660] [c000000109703c00] [c0000000004707c0] do_iter_
16:20:39 DEBUG| [stdout] [ 6521.210735] [c000000109703c70] [c0000000004730d8] do_iter_
16:20:39 DEBUG| [stdout] [ 6521.210794] [c000000109703cc0] [c0000000004733a0] vfs_writev+
16:20:39 DEBUG| [stdout] [ 6521.210854] [c000000109703dc0] [c0000000004734dc] do_writev+
16:20:39 DEBUG| [stdout] [ 6521.210915] [c000000109703e20] [c00000000000b278] system_
16:20:39 DEBUG| [stdout] [ 6521.210973] Instruction dump:
16:20:39 DEBUG| [stdout] [ 6521.211018] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
16:20:39 DEBUG| [stdout] [ 6521.211089] XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX
16:20:39 DEBUG| [stdout] [ 6521.211168] ---[ end trace 141e6d1cc5d48ea2 ]---
Full testing log:
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
I've seen something very similar to this on this platform and I believe it's a combination of previous regressions tests and the stress-ng sysinfo test that triggers this. Running the stress-ng stressor after a clean boot won't trigger this issue.