[lkml]   [2022]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 6.1-rc1
On Sun, Oct 16, 2022 at 04:01:33PM -0700, Linus Torvalds wrote:
> You all know the drill: it's Sunday afternoon, the two weeks of merge
> window are over, and now we're supposed to start calming things down.
[ ... ]

> Please get the testing started,

Build results:
total: 152 pass: 152 fail: 0
Qemu test results:
total: 490 pass: 420 fail: 70
Failed tests:
<all big endian mips tests>
<all riscv tests>

The following patches are needed to fix the problems reported below.

Revert "net: fix cpu_max_bits_warn() usage in netif_attrmask_next{,_and}"
Revert "mfd: syscon: Remove repetition of the regmap_get_val_endian()"
RISC-V: KVM: Fix compilation without RISCV_ISA_ZICBOM
powerpc/64s: make linear_map_hash_lock a raw spinlock
powerpc/64s: make HPTE lock and native_tlbie_lock irq-safe
powerpc/64s: Add lockdep for HPTE lock
powerpc: fix reschedule bug in KUAP-unlocked user copy
powerpc/64s: Fix hash__change_memory_range preemption warning
powerpc/64s: Disable preemption in hash lazy mmu mode

Build failures

Building riscv:defconfig ... failed
Error log:
ERROR: modpost: "riscv_cbom_block_size" [arch/riscv/kvm/kvm.ko] undefined!

Caused by commit afd5dde9a186 ("RISC-V: KVM: Provide UAPI for Zicbom block
size"). Suggested fix is at
Last time I checked (10/14) it was still under discussion.

Cc: Andrew Jones <>
Cc: Conor Dooley <>
Cc: Atish Patra <>
Cc: Anup Patel <>


Runtime failures / warnings


BUG: using smp_processor_id() in preemptible [00000000] code: swapper/0/1
caller is .__apply_to_page_range+0x734/0xa20
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.0.0-12130-g73344a3f6793 #1
Hardware name: PowerMac3,1 PPC970FX 0x3c0301 PowerMac
Call Trace:
[c0000000056075b0] [c000000001085308] .dump_stack_lvl+0xa4/0x100 (unreliable)
[c000000005607640] [c0000000010ba384] .check_preemption_disabled+0x144/0x150
[c0000000056076e0] [c000000000371464] .__apply_to_page_range+0x734/0xa20
[c000000005607820] [c00000000006e21c] .change_memory_attr+0xfc/0x160
[c0000000056078b0] [c0000000002ce778] .bpf_prog_select_runtime+0x78/0x220
[c000000005607950] [c000000000de3a68] .bpf_prepare_filter+0xa18/0xa80
[c000000005607a10] [c000000000de3b6c] .bpf_prog_create+0x9c/0x110
[c000000005607aa0] [c00000000205e0c4] .ptp_classifier_init+0x44/0x78
[c000000005607b30] [c00000000205d260] .sock_init+0xd8/0xf8
[c000000005607bb0] [c000000000010e28] .do_one_initcall+0xa8/0x528
[c000000005607ca0] [c00000000200501c] .kernel_init_freeable+0x3c8/0x478
[c000000005607d90] [c0000000000116bc] .kernel_init+0x2c/0x1c0
[c000000005607e10] [c00000000000ca3c] .ret_from_kernel_thread+0x58/0x60

Not a new problem (seen as far back as v5.15.y), but fixed by:
"powerpc/64s: Disable preemption in hash lazy mmu mode"
"powerpc/64s: Fix hash__change_memory_range preemption warning"
"powerpc: fix reschedule bug in KUAP-unlocked user copy"


WARNING: inconsistent lock state
6.0.0-12130-g73344a3f6793 #1 Tainted: G N
inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage.
swapper/0/1 [HC0[0]:SC0[0]:HE1:SE1] takes:
c000000002734de8 (native_tlbie_lock){+.?.}-{2:2}, at: .native_hpte_updateboltedpp+0x1a4/0x600
{IN-SOFTIRQ-W} state was registered at:

Fixed by:
"powerpc/64s: Add lockdep for HPTE lock"
"powerpc/64s: make HPTE lock and native_tlbie_lock irq-safe"
"powerpc/64s: make linear_map_hash_lock a raw spinlock:


mips, sparc64

All big endian mips tests fail to reset after boot. The problem is
caused by commit 72a95859728a ("mfd: syscon: Remove repetition of the

Cc: Hector Martin <>
Cc: Arnd Bergmann <>
Cc: Lee Jones <>

The riscv build failure is hiding a new runtime warning, seen with
32-bit and 64-bit riscv boot tests after the fix for the build problem
was applied.

------------[ cut here ]------------
WARNING: CPU: 0 PID: 1 at include/linux/cpumask.h:110 __netif_set_xps_queue+0x194/0x976
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.0.0-12199-g277163563de8 #1
Hardware name: riscv-virtio,qemu (DT)
epc : __netif_set_xps_queue+0x194/0x976
ra : __netif_set_xps_queue+0x3b0/0x976
epc : c089a664 ra : c089a880 sp : c2515c60
gp : c1d8e760 tp : c2578040 t0 : c364f980
t1 : 00000000 t2 : 00001fff s0 : c2515cd0
s1 : c2515ce4 a0 : c364f940 a1 : 00000000
a2 : c364f940 a3 : 00000000 a4 : c364f950
a5 : c364f890 a6 : 00000003 a7 : 00000000
s2 : 00000001 s3 : c1d382c0 s4 : 00000000
s5 : 00000000 s6 : 00000000 s7 : c364f880
s8 : 00000000 s9 : 00000001 s10: 00000001
s11: 00000000 t3 : 00000018 t4 : 7fd38a0e
t5 : 00000007 t6 : c3639470
status: 00000120 badaddr: 00000000 cause: 00000003
[<c074548a>] virtnet_set_affinity+0x13a/0x1a2
[<c07478de>] virtnet_probe+0x884/0xfdc
[<c063ce9a>] virtio_dev_probe+0x1d6/0x354
[<c0683d6e>] really_probe+0x82/0x214
[<c0683f58>] __driver_probe_device+0x58/0xa2
[<c0683fd2>] driver_probe_device+0x30/0xaa
[<c0684596>] __driver_attach+0x56/0x11c
[<c0681f26>] bus_for_each_dev+0x52/0x90
[<c06837c0>] driver_attach+0x1a/0x22
[<c068331a>] bus_add_driver+0x148/0x1b6
[<c0684d70>] driver_register+0x52/0xea
[<c063c924>] register_virtio_driver+0x1a/0x28
[<c0c2428e>] virtio_net_driver_init+0x7a/0xa6
[<c0002824>] do_one_initcall+0x5e/0x2e2
[<c0c01130>] kernel_init_freeable+0x298/0x306
[<c0aa0ac2>] kernel_init+0x1e/0x10e
[<c0003ad8>] ret_from_exception+0x0/0x10
irq event stamp: 106012
hardirqs last enabled at (106011): [<c0aa9284>] _raw_spin_unlock_irqrestore+0x54/0x62
hardirqs last disabled at (106012): [<c0007534>] __trace_hardirqs_off+0xc/0x14
softirqs last enabled at (105764): [<c0886392>] napi_get_frags_check+0x0/0x50
softirqs last disabled at (105758): [<c0886392>] napi_get_frags_check+0x0/0x50
---[ end trace 0000000000000000 ]---

This is is caused (triggered ? exposed ?) by commit 854701ba4c39
("net: fix cpu_max_bits_warn() usage in netif_attrmask_next{,_and}").

A revert for this patch is at:

This revert has been applied to the net tree.

Cc: Yury Norov <>
Cc: Andy Shevchenko <>
Cc: Rasmus Villemoes <>
Cc: Guo Ren <>
Cc: Jakub Kicinski <>

 \ /
  Last update: 2022-10-17 14:35    [W:0.124 / U:1.576 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site