Message-ID: <00000000000049e78d061073467c@google.com>
Date: Fri, 02 Feb 2024 21:12:26 -0800
From: syzbot <syzbot+f91f2ed0a5258704982f@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, 
	sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [kernel?] linux-next boot error: WARNING in wq_update_node_max_active

Hello,

syzbot found the following issue on:

HEAD commit:    06f658aadff0 Add linux-next specific files for 20240131
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14882997e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=854ef3e6fbbe979f
dashboard link: https://syzkaller.appspot.com/bug?extid=f91f2ed0a5258704982f
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7b4f22c20549/disk-06f658aa.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9150a87d7432/vmlinux-06f658aa.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a572351012f3/bzImage-06f658aa.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f91f2ed0a5258704982f@...kaller.appspotmail.com

Initmem setup node 0 [mem 0x0000000000001000-0x000000013fffffff]
Initmem setup node 1 [mem 0x0000000140000000-0x000000023fffffff]
On node 0, zone DMA: 1 pages in unavailable ranges
On node 0, zone DMA: 97 pages in unavailable ranges
On node 0, zone Normal: 3 pages in unavailable ranges
kasan: KernelAddressSanitizer initialized
ACPI: PM-Timer IO Port: 0xb008
ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
ACPI: Using ACPI (MADT) for SMP configuration information
smpboot: Allowing 2 CPUs, 0 hotplug CPUs
PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000effff]
PM: hibernation: Registered nosave memory: [mem 0x000f0000-0x000fffff]
PM: hibernation: Registered nosave memory: [mem 0xbfffd000-0xbfffffff]
PM: hibernation: Registered nosave memory:serialport: Connected to syzkaller.us-central1-c.ci-upstream-linux-next-kasan-gce-root-test-1 port 1 (session ID: 307732399ece189a8aef52b22bfe9e76c226ee4a91fad6ea856fd1c30fec1568, active connections: 1).
PM: hibernation: Registered nosave memory: [mem 0xfffbc000-0xffffffff]
[mem 0xc0000000-0xfffbbfff] available for PCI devices
Booting paravirtualized kernel on KVM
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
setup_percpu: NR_CPUS:8 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:2
percpu: Embedded 72 pages/cpu s256200 r8192 d30520 u1048576
kvm-guest: PV spinlocks enabled
PV qspinlock hash table entries: 256 (order: 0, 4096 bytes, linear)
Kernel command line: earlyprintk=serial net.ifnames=0 sysctl.kernel.hung_task_all_cpu_backtrace=1 ima_policy=tcb nf-conntrack-ftp.ports=20000 nf-conntrack-tftp.ports=20000 nf-conntrack-sip.ports=20000 nf-conntrack-irc.ports=20000 nf-conntrack-sane.ports=20000 binder.debug_mask=0 rcupdate.rcu_expedited=1 rcupdate.rcu_cpu_stall_cputime=1 no_hash_pointers page_owner=on sysctl.vm.nr_hugepages=4 sysctl.vm.nr_overcommit_hugepages=4 secretmem.enable=1 sysctl.max_rcu_stall_to_panic=1 msr.allow_writes=off coredump_filter=0xffff root=/dev/sda console=ttyS0 vsyscall=native numa=fake=2 kvm-intel.nested=1 spec_store_bypass_disable=prctl nopcid vivid.n_devs=16 vivid.multiplanar=1,2,1,2,1,2,1,2,1,2,1,2,1,2,1,2 netrom.nr_ndevs=16 rose.rose_ndevs=16 smp.csd_lock_timeout=100000 watchdog_thresh=55 workqueue.watchdog_thresh=140 sysctl.net.core.netdev_unregister_timeout_secs=140 dummy_hcd.num=8 panic_on_warn=1 BOOT_IMAGE=/boot/bzImage root=/dev/sda1 console=ttyS0
Unknown kernel command line parameters "spec_store_bypass_disable=prctl BOOT_IMAGE=/boot/bzImage", will be passed to user space.
random: crng init done
Fallback order for Node 0: 0 1 
Fallback order for Node 1: 1 0 
Built 2 zonelists, mobility grouping on.  Total pages: 2064125
Policy zone: Normal
mem auto-init: stack:all(zero), heap alloc:on, heap free:off
stackdepot: allocating hash table via alloc_large_system_hash
stackdepot hash table entries: 1048576 (order: 12, 16777216 bytes, linear)
software IO TLB: area num 2.
Memory: 6760000K/8388204K available (163840K kernel code, 38961K rwdata, 36628K rodata, 25688K init, 33252K bss, 1627948K reserved, 0K cma-reserved)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=2
allocated 167772160 bytes of page_ext
Node 0, zone      DMA: page owner found early allocated 0 pages
Node 0, zone    DMA32: page owner found early allocated 20599 pages
Node 0, zone   Normal: page owner found early allocated 0 pages
Node 1, zone   Normal: page owner found early allocated 20484 pages
Kernel/User page tables isolation: enabled
Dynamic Preempt: full
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at include/linux/cpumask.h:143 cpu_max_bits_warn include/linux/cpumask.h:143 [inline]
WARNING: CPU: 0 PID: 0 at include/linux/cpumask.h:143 cpumask_check include/linux/cpumask.h:150 [inline]
WARNING: CPU: 0 PID: 0 at include/linux/cpumask.h:143 cpumask_test_cpu include/linux/cpumask.h:516 [inline]
WARNING: CPU: 0 PID: 0 at include/linux/cpumask.h:143 wq_update_node_max_active+0x636/0x780 kernel/workqueue.c:1513
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-rc2-next-20240131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:cpu_max_bits_warn include/linux/cpumask.h:143 [inline]
RIP: 0010:cpumask_check include/linux/cpumask.h:150 [inline]
RIP: 0010:cpumask_test_cpu include/linux/cpumask.h:516 [inline]
RIP: 0010:wq_update_node_max_active+0x636/0x780 kernel/workqueue.c:1513
Code: ed 71 09 31 ff 89 c3 89 c6 e8 46 65 34 00 85 db 0f 85 0d fb ff ff e8 59 6a 34 00 90 0f 0b 90 e9 ff fa ff ff e8 4b 6a 34 00 90 <0f> 0b 90 e9 1c fb ff ff 48 89 df e8 fa f8 8e 00 e9 48 fd ff ff 48
RSP: 0000:ffffffff8d407c08 EFLAGS: 00010093
RAX: 0000000000000000 RBX: 00000000ffffffff RCX: ffffffff81585961
RDX: ffffffff8d495a40 RSI: ffffffff81585e45 RDI: 0000000000000005
RBP: ffff888014c91da0 R08: 0000000000000005 R09: 0000000000000007
R10: 00000000ffffffff R11: 0000000000000001 R12: ffff888014c99000
R13: 0000000000000200 R14: ffff888014c91db0 R15: 0000000000000002
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000d57a000 CR4: 00000000000000b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 apply_wqattrs_commit+0x430/0x590 kernel/workqueue.c:4844
 apply_workqueue_attrs_locked+0xf3/0x160 kernel/workqueue.c:4871
 apply_workqueue_attrs kernel/workqueue.c:4902 [inline]
 alloc_and_link_pwqs kernel/workqueue.c:5023 [inline]
 alloc_workqueue+0x1256/0x1a90 kernel/workqueue.c:5232
 workqueue_init_early+0xcb4/0x1080 kernel/workqueue.c:7218
 start_kernel+0x199/0x480 init/main.c:958
 x86_64_start_reservations+0x18/0x30 arch/x86/kernel/head64.c:555
 x86_64_start_kernel+0xb2/0xc0 arch/x86/kernel/head64.c:536
 secondary_startup_64_no_verify+0x170/0x17b
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

Powered by blists - more mailing lists