[v6.1] INFO: rcu detected stall in kcov_close

0 views
Skip to first unread message

syzbot

unread,
May 26, 2024, 5:21:25 AMMay 26
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e83ae8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=649b1969512ce3734fde
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/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-....: (1 ticks this GP) idle=7d74/1/0x4000000000000000 softirq=15287/15287 fqs=7
(detected by 1, t=10502 jiffies, g=17997, q=998 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 5567 Comm: syz-executor.2 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:228 [inline]
RIP: 0010:check_wait_context kernel/locking/lockdep.c:4723 [inline]
RIP: 0010:__lock_acquire+0x49d/0x1f80 kernel/locking/lockdep.c:4999
Code: 12 00 00 44 89 33 44 89 fb 48 89 d8 48 c1 e8 06 48 8d 3c c5 20 c2 49 90 be 08 00 00 00 e8 eb a1 77 00 48 0f a3 1d a3 55 df 0e <73> 25 48 8d 04 5b 48 c1 e0 06 48 8d 98 20 21 19 90 48 ba 00 00 00
RSP: 0000:ffffc90000007a60 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 000000000000099b RCX: ffffffff816a6c75
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9049c350
RBP: ffff888056eca884 R08: dffffc0000000000 R09: fffffbfff209386b
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888056eca898
R13: ffff888056ec9dc0 R14: 0000000000000000 R15: 000000000000099b
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3bd4e60bd0 CR3: 000000007946d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
advance_sched+0x47/0x970 net/sched/sch_taprio.c:700
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:unwind_next_frame+0x152/0x2220
Code: fc ff df 0f b6 44 3d 00 84 c0 0f 85 93 1a 00 00 48 89 9c 24 90 00 00 00 4c 0f be 2b 48 8b 44 24 30 80 3c 38 00 48 8b 5c 24 18 <74> 0e 49 89 fe 48 89 df e8 c1 67 a5 00 4c 89 f7 4c 03 2b 49 ff cd
RSP: 0000:ffffc9000b04f280 EFLAGS: 00000246
RAX: 1ffff92001609e75 RBX: ffffc9000b04f3a8 RCX: ffffffff8a957800
RDX: dffffc0000000000 RSI: ffffffff815376b3 RDI: dffffc0000000000
RBP: 1ffff92001609e72 R08: 0000000000000006 R09: ffffc9000b04f450
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888056ec9dc0
R13: 0000000000000000 R14: dffffc0000000000 R15: ffffffff815376b3
arch_stack_walk+0x10d/0x140 arch/x86/kernel/stacktrace.c:25
stack_trace_save+0x113/0x1c0 kernel/stacktrace.c:122
save_stack+0xf6/0x1e0 mm/page_owner.c:127
__reset_page_owner+0x52/0x1a0 mm/page_owner.c:148
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1440 [inline]
free_pcp_prepare mm/page_alloc.c:1490 [inline]
free_unref_page_prepare+0xf63/0x1120 mm/page_alloc.c:3358
free_unref_page+0x33/0x3e0 mm/page_alloc.c:3453
__vunmap+0x834/0x9a0 mm/vmalloc.c:2717
kcov_put kernel/kcov.c:428 [inline]
kcov_close+0x27/0x50 kernel/kcov.c:524
__fput+0x3b7/0x890 fs/file_table.c:320
task_work_run+0x246/0x300 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xa73/0x26a0 kernel/exit.c:869
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
get_signal+0x16f7/0x17d0 kernel/signal.c:2862
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:303
ret_from_fork+0x15/0x30 arch/x86/entry/entry_64.S:301
RIP: 0033:0x7efd79ea8cd9
Code: Unable to access opcode bytes at 0x7efd79ea8caf.
RSP: 002b:00007efd7ac42240 EFLAGS: 00000202 ORIG_RAX: 00000000000001b3
RAX: 0000000000000000 RBX: 00007efd79e513b0 RCX: 00007efd79ea8cd9
RDX: 00007efd79e513b0 RSI: 0000000000000058 RDI: 00007ffdb9b14990
RBP: 00007efd7ac426c0 R08: 00007efd7ac426c0 R09: 00007ffdb9b14a77
R10: 0000000000000008 R11: 0000000000000202 R12: ffffffffffffffb0
R13: 000000000000006e R14: 00007ffdb9b14990 R15: 00007ffdb9b14a78
</TASK>
rcu: rcu_preempt kthread timer wakeup didn't happen for 377 jiffies! g17997 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402
rcu: Possible timer handling issue on cpu=1 timer-softirq=8403
rcu: rcu_preempt kthread starved for 378 jiffies! g17997 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->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:I stack:26680 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1965
rcu_gp_fqs_loop+0x2d2/0x1150 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3b0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 1 PID: 3617 Comm: kworker/1:8 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
Workqueue: events drain_vmap_area_work
RIP: 0010:csd_lock_wait kernel/smp.c:424 [inline]
RIP: 0010:smp_call_function_many_cond+0x1fb0/0x3460 kernel/smp.c:998
Code: 2f 44 89 ee 83 e6 01 31 ff e8 ec 42 0b 00 41 83 e5 01 49 bd 00 00 00 00 00 fc ff df 75 0a e8 77 3f 0b 00 e9 1b ff ff ff f3 90 <42> 0f b6 04 2b 84 c0 75 14 41 f7 07 01 00 00 00 0f 84 fe fe ff ff
RSP: 0018:ffffc900040ff6e0 EFLAGS: 00000293
RAX: ffffffff817f4dfb RBX: 1ffff1101730859d RCX: ffff888025611dc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900040ffac0 R08: ffffffff817f4dc4 R09: fffffbfff2093846
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880b9842ce8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3bd4f35348 CR3: 0000000016b58000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1166
__purge_vmap_area_lazy+0x29c/0x1720 mm/vmalloc.c:1753
drain_vmap_area_work+0x3c/0xd0 mm/vmalloc.c:1803
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
worker_thread+0xa47/0x1200 kernel/workqueue.c:2439
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</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 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 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