Message-ID: <67548a2c.050a0220.2477f.001a.GAE@google.com>
Date: Sat, 07 Dec 2024 09:47:24 -0800
From: syzbot <syzbot+4dbab151c88eb889644b@...kaller.appspotmail.com>
To: Liam.Howlett@...cle.com, akpm@...ux-foundation.org, jannh@...gle.com, 
	linux-kernel@...r.kernel.org, linux-mm@...ck.org, lorenzo.stoakes@...cle.com, 
	syzkaller-bugs@...glegroups.com, vbabka@...e.cz
Subject: [syzbot] [mm?] upstream test error: WARNING: locking bug in __rmqueue_pcplist

Hello,

syzbot found the following issue on:

HEAD commit:    ceb8bf2ceaa7 module: Convert default symbol namespace to s..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13cef5e8580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6271abc57260d634
dashboard link: https://syzkaller.appspot.com/bug?extid=4dbab151c88eb889644b
compiler:       aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-ceb8bf2c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/30e29cf33ebb/vmlinux-ceb8bf2c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee2d212ca202/zImage-ceb8bf2c.xz

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

=============================
[ BUG: Invalid wait context ]
6.13.0-rc1-syzkaller-00005-gceb8bf2ceaa7 #0 Not tainted
-----------------------------
syz.0.40/3323 is trying to lock:
ffff00007fc1ffd8 (&zone->lock){..-.}-{3:3}, at: rmqueue_bulk mm/page_alloc.c:2307 [inline]
ffff00007fc1ffd8 (&zone->lock){..-.}-{3:3}, at: __rmqueue_pcplist+0x388/0x1178 mm/page_alloc.c:3001
other info that might help us debug this:
context-{2:2}
4 locks held by syz.0.40/3323:
 #0: ffff0000171eed10 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:144 [inline]
 #0: ffff0000171eed10 (&mm->mmap_lock){++++}-{4:4}, at: exit_mmap+0xe4/0x94c mm/mmap.c:1651
 #1: ffff800086f89760 (rcu_read_lock){....}-{1:3}, at: __pte_offset_map+0x0/0x290 mm/pgtable-generic.c:253
 #2: ffff00000fbdcc78 (ptlock_ptr(ptdesc)){+.+.}-{3:3}, at: spin_lock include/linux/spinlock.h:351 [inline]
 #2: ffff00000fbdcc78 (ptlock_ptr(ptdesc)){+.+.}-{3:3}, at: __pte_offset_map_lock+0x118/0x2ec mm/pgtable-generic.c:402
 #3: ffff000069f98698 (&pcp->lock){+.+.}-{3:3}, at: spin_trylock include/linux/spinlock.h:361 [inline]
 #3: ffff000069f98698 (&pcp->lock){+.+.}-{3:3}, at: rmqueue_pcplist mm/page_alloc.c:3030 [inline]
 #3: ffff000069f98698 (&pcp->lock){+.+.}-{3:3}, at: rmqueue mm/page_alloc.c:3074 [inline]
 #3: ffff000069f98698 (&pcp->lock){+.+.}-{3:3}, at: get_page_from_freelist+0x428/0x20f0 mm/page_alloc.c:3471
stack backtrace:
CPU: 1 UID: 0 PID: 3323 Comm: syz.0.40 Not tainted 6.13.0-rc1-syzkaller-00005-gceb8bf2ceaa7 #0
Hardware name: linux,dummy-virt (DT)
Call trace:
 show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:484 (C)
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0xa4/0xf4 lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_lock_invalid_wait_context kernel/locking/lockdep.c:4826 [inline]
 check_wait_context kernel/locking/lockdep.c:4898 [inline]
 __lock_acquire+0x1514/0x6604 kernel/locking/lockdep.c:5176
 lock_acquire kernel/locking/lockdep.c:5849 [inline]
 lock_acquire+0x450/0x76c kernel/locking/lockdep.c:5814
 __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline]
 _raw_spin_lock_irqsave+0x58/0x80 kernel/locking/spinlock.c:162
 rmqueue_bulk mm/page_alloc.c:2307 [inline]
 __rmqueue_pcplist+0x388/0x1178 mm/page_alloc.c:3001
 rmqueue_pcplist mm/page_alloc.c:3043 [inline]
 rmqueue mm/page_alloc.c:3074 [inline]
 get_page_from_freelist+0x4a0/0x20f0 mm/page_alloc.c:3471
 __alloc_pages_noprof+0x1b4/0x2248 mm/page_alloc.c:4751
 alloc_pages_mpol_noprof+0x104/0x490 mm/mempolicy.c:2265
 alloc_pages_noprof+0x178/0x1ec mm/mempolicy.c:2344
 stack_depot_save_flags+0x508/0x95c lib/stackdepot.c:627
 kasan_save_stack+0x50/0x64 mm/kasan/common.c:48
 __kasan_record_aux_stack+0xa0/0xb8 mm/kasan/generic.c:544
 kasan_record_aux_stack+0x14/0x20 mm/kasan/generic.c:549
 task_work_add+0x9c/0x35c kernel/task_work.c:77
 __run_posix_cpu_timers kernel/time/posix-cpu-timers.c:1223 [inline]
 run_posix_cpu_timers+0x51c/0x810 kernel/time/posix-cpu-timers.c:1422
 update_process_times+0x16c/0x444 kernel/time/timer.c:2526
 tick_sched_handle kernel/time/tick-sched.c:276 [inline]
 tick_nohz_handler+0x198/0x40c kernel/time/tick-sched.c:297
 __run_hrtimer kernel/time/hrtimer.c:1739 [inline]
 __hrtimer_run_queues+0x5ec/0x964 kernel/time/hrtimer.c:1803
 hrtimer_interrupt+0x2a0/0x768 kernel/time/hrtimer.c:1865
 timer_handler drivers/clocksource/arm_arch_timer.c:674 [inline]
 arch_timer_handler_phys+0x40/0x6c drivers/clocksource/arm_arch_timer.c:692
 handle_percpu_devid_irq+0x19c/0x30c kernel/irq/chip.c:942
 generic_handle_irq_desc include/linux/irqdesc.h:173 [inline]
 handle_irq_desc kernel/irq/irqdesc.c:714 [inline]
 generic_handle_domain_irq+0x78/0xa4 kernel/irq/irqdesc.c:770
 gic_handle_irq+0x54/0x184 drivers/irqchip/irq-gic.c:370
 call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:891
 do_interrupt_handler+0x12c/0x150 arch/arm64/kernel/entry-common.c:310
 __el1_irq arch/arm64/kernel/entry-common.c:560 [inline]
 el1_interrupt+0x34/0x54 arch/arm64/kernel/entry-common.c:575
 el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:580
 el1h_64_irq+0x6c/0x70 arch/arm64/kernel/entry.S:596
 __kasan_check_write+0x20/0x2c mm/kasan/shadow.c:37 (P)
 __kasan_check_write+0x20/0x2c mm/kasan/shadow.c:37 (L)
 instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
 atomic_add_negative include/linux/atomic/atomic-instrumented.h:1420 [inline]
 __folio_remove_rmap mm/rmap.c:1547 [inline]
 folio_remove_rmap_ptes+0x6c/0x380 mm/rmap.c:1620
 zap_present_folio_ptes mm/memory.c:1526 [inline]
 zap_present_ptes mm/memory.c:1585 [inline]
 zap_pte_range mm/memory.c:1627 [inline]
 zap_pmd_range mm/memory.c:1753 [inline]
 zap_pud_range mm/memory.c:1782 [inline]
 zap_p4d_range mm/memory.c:1803 [inline]
 unmap_page_range+0xe38/0x2318 mm/memory.c:1824
 unmap_single_vma.constprop.0+0xb4/0x188 mm/memory.c:1870
 unmap_vmas+0x194/0x318 mm/memory.c:1914
 exit_mmap+0x138/0x94c mm/mmap.c:1667
 __mmput+0xa8/0x39c kernel/fork.c:1353
 mmput+0x88/0x98 kernel/fork.c:1375
 exit_mm kernel/exit.c:570 [inline]
 do_exit+0x6d4/0x2048 kernel/exit.c:925
 do_group_exit+0xa4/0x208 kernel/exit.c:1087
 __do_sys_exit_group kernel/exit.c:1098 [inline]
 __se_sys_exit_group kernel/exit.c:1096 [inline]
 __arm64_sys_exit_group+0x3c/0x44 kernel/exit.c:1096
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x6c/0x258 arch/arm64/kernel/syscall.c:49
 el0_svc_common.constprop.0+0xac/0x230 arch/arm64/kernel/syscall.c:132
 do_el0_svc_compat+0x40/0x68 arch/arm64/kernel/syscall.c:157
 el0_svc_compat+0x4c/0x17c arch/arm64/kernel/entry-common.c:887
 el0t_32_sync_handler+0x98/0x13c arch/arm64/kernel/entry-common.c:897
 el0t_32_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:605


---
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