[v5.15] INFO: rcu detected stall in filemap_fault (2)

0 views
Skip to first unread message

syzbot

unread,
Feb 27, 2025, 4:48:30 PMFeb 27
Hello,

syzbot found the following issue on:

HEAD commit: c16c81c81336 Linux 5.15.178
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1581c064580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d302c69e93fb6774
dashboard link: https://syzkaller.appspot.com/bug?extid=36b496a0a96ab7d07287
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/267e46ee7273/disk-c16c81c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/944e289206cf/vmlinux-c16c81c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f8cadf62458e/bzImage-c16c81c8.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P4621/1:b..l
(detected by 0, t=10502 jiffies, g=10205, q=266)
task:syz.2.66 state:R running task stack:22296 pid: 4621 ppid: 4617 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5027 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6777
irqentry_exit+0x53/0x80 kernel/entry/common.c:432
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:lock_acquire+0x252/0x4f0 kernel/locking/lockdep.c:5627
Code: 2b 00 74 08 4c 89 f7 e8 9c 9e 67 00 f6 44 24 61 02 0f 85 84 01 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 c7 44 24 40 0e 36 e0 45 <4b> c7 44 25 00 00 00 00 00 43 c7 44 25 09 00 00 00 00 43 c7 44 25
RSP: 0018:ffffc9000137e600 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 1ffff9200026fccc RCX: 1ffff9200026fc6c
RDX: dffffc0000000000 RSI: ffffffff8aab3e20 RDI: ffffffff8af9f2c0
RBP: ffffc9000137e760 R08: dffffc0000000000 R09: fffffbfff2131821
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff9200026fcc8
R13: dffffc0000000000 R14: ffffc9000137e660 R15: 0000000000000246
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:312
rcu_read_lock include/linux/rcupdate.h:739 [inline]
xa_get_order+0x150/0x550 lib/xarray.c:1764
__add_to_page_cache_locked+0x60c/0x11a0 mm/filemap.c:901
add_to_page_cache_lru+0x1b3/0x560 mm/filemap.c:984
page_cache_ra_unbounded+0x403/0x930 mm/readahead.c:222
page_cache_async_readahead include/linux/pagemap.h:856 [inline]
do_async_mmap_readahead mm/filemap.c:3023 [inline]
filemap_fault+0x669/0x1470 mm/filemap.c:3079
__do_fault+0x139/0x340 mm/memory.c:3926
do_read_fault mm/memory.c:4262 [inline]
do_fault mm/memory.c:4390 [inline]
handle_pte_fault mm/memory.c:4648 [inline]
__handle_mm_fault mm/memory.c:4783 [inline]
handle_mm_fault+0x376f/0x5960 mm/memory.c:4881
faultin_page mm/gup.c:976 [inline]
__get_user_pages+0x4ed/0x11d0 mm/gup.c:1197
__get_user_pages_locked mm/gup.c:1382 [inline]
get_dump_page+0x1ad/0x8a0 mm/gup.c:1838
dump_user_range+0x64/0x320 fs/coredump.c:945
elf_core_dump+0x3c7d/0x4570 fs/binfmt_elf.c:2285
do_coredump+0x1852/0x31e0 fs/coredump.c:826
get_signal+0xc06/0x14e0 kernel/signal.c:2886
arch_do_signal_or_restart+0xc3/0x1890 arch/x86/kernel/signal.c:867
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x97/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
irqentry_exit_to_user_mode+0x5/0x30 kernel/entry/common.c:320
exc_general_protection+0x358/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:600
RIP: 0033:0x7f88f2793171
RSP: 002b:0000400000000120 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 00007f88f29abfa0 RCX: 00007f88f2793169
RDX: 0000400000000180 RSI: 0000400000000120 RDI: 0000000000300000
RBP: 00007f88f28142a0 R08: 0000400000000240 R09: 0000400000000240
R10: 00004000000001c0 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f88f29abfa0 R15: 00007ffd575b1728
</TASK>
rcu: rcu_preempt kthread starved for 10378 jiffies! g10205 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:27064 pid: 15 ppid: 2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5027 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6373
schedule+0x11b/0x1f0 kernel/sched/core.c:6456
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1914
rcu_gp_fqs_loop+0x2bf/0x1080 kernel/rcu/tree.c:1972
rcu_gp_kthread+0xa4/0x360 kernel/rcu/tree.c:2145
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:108 [inline]
NMI backtrace for cpu 1 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:562


---
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 [email protected].

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
Reply all
Reply to author
Forward
0 new messages