Hello,
syzbot found the following issue on:
HEAD commit: 0a51d2d4527b Linux 5.15.173
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17625f78580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=69147a3052c29ea2
dashboard link:
https://syzkaller.appspot.com/bug?extid=4f1638fef5ef98110679
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=137480df980000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/cbeb11c653b7/disk-0a51d2d4.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/3b646052737b/vmlinux-0a51d2d4.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/0f7e7bafd5b2/Image-0a51d2d4.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+4f1638...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt self-detected stall on CPU
rcu: 0-...!: (1 GPs behind) idle=0a3/1/0x4000000000000002 softirq=6298/6302 fqs=7
(t=10501 jiffies g=5557 q=337)
rcu: rcu_preempt kthread starved for 10487 jiffies! g5557 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: 0 pid: 15 ppid: 2 flags:0x00000008
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
context_switch kernel/sched/core.c:5027 [inline]
__schedule+0xf10/0x1e48 kernel/sched/core.c:6373
schedule+0x11c/0x1c8 kernel/sched/core.c:6456
schedule_timeout+0x1d8/0x344 kernel/time/timer.c:1914
rcu_gp_fqs_loop+0x26c/0x13d4 kernel/rcu/tree.c:1972
rcu_gp_kthread+0xc4/0x2c4 kernel/rcu/tree.c:2145
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
rcu: Stack dump where RCU GP kthread last ran:
Task dump for CPU 1:
task:syz.0.15 state:R running task stack: 0 pid: 4190 ppid: 4107 flags:0x00000000
Call trace:
__switch_to+0x308/0x5e8 arch/arm64/kernel/process.c:518
mark_usage kernel/locking/lockdep.c:4512 [inline]
__lock_acquire+0xc44/0x7638 kernel/locking/lockdep.c:4966
return_address+0x0/0x1ec
Task dump for CPU 0:
task:syz.3.25 state:R running task stack: 0 pid: 4188 ppid: 4123 flags:0x00000000
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
sched_show_task+0x43c/0x574 kernel/sched/core.c:8637
dump_cpu_task+0x84/0xa8 kernel/sched/core.c:10924
rcu_dump_cpu_stacks+0x2d8/0x540 kernel/rcu/tree_stall.h:350
print_cpu_stall+0x558/0xc7c kernel/rcu/tree_stall.h:633
check_cpu_stall kernel/rcu/tree_stall.h:727 [inline]
rcu_pending kernel/rcu/tree.c:3932 [inline]
rcu_sched_clock_irq+0xd20/0x1b8c kernel/rcu/tree.c:2619
update_process_times+0x1d4/0x270 kernel/time/timer.c:1818
tick_sched_handle kernel/time/tick-sched.c:254 [inline]
tick_sched_timer+0x340/0x4f8 kernel/time/tick-sched.c:1473
__run_hrtimer kernel/time/hrtimer.c:1688 [inline]
__hrtimer_run_queues+0x458/0xca4 kernel/time/hrtimer.c:1752
hrtimer_interrupt+0x2c0/0xb64 kernel/time/hrtimer.c:1814
timer_handler drivers/clocksource/arm_arch_timer.c:659 [inline]
arch_timer_handler_virt+0x74/0x88 drivers/clocksource/arm_arch_timer.c:670
handle_percpu_devid_irq+0x29c/0x7fc kernel/irq/chip.c:930
generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
handle_irq_desc kernel/irq/irqdesc.c:652 [inline]
handle_domain_irq+0xec/0x178 kernel/irq/irqdesc.c:707
gic_handle_irq+0x78/0x1c8 drivers/irqchip/irq-gic-v3.c:765
call_on_irq_stack+0x24/0x4c arch/arm64/kernel/entry.S:899
do_interrupt_handler+0x74/0x94 arch/arm64/kernel/entry-common.c:267
el1_interrupt+0x30/0x58 arch/arm64/kernel/entry-common.c:454
el1h_64_irq_handler+0x18/0x24 arch/arm64/kernel/entry-common.c:470
el1h_64_irq+0x78/0x7c arch/arm64/kernel/entry.S:522
pid_nr_ns kernel/pid.c:479 [inline]
__task_pid_nr_ns+0x24c/0x420 kernel/pid.c:500
task_tgid_vnr include/linux/sched.h:1587 [inline]
__arm64_sys_getpid+0x20/0x30 kernel/sys.c:945
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
---
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
syzk...@googlegroups.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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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