syzbot


INFO: rcu detected stall in sys_exit_group

Status: auto-obsoleted due to no activity on 2023/08/23 09:06
Reported-by: syzbot+7a7e83335faf8fb7167f@syzkaller.appspotmail.com
First crash: 407d, last: 407d
Similar bugs (12)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: rcu detected stall in sys_exit_group (7) net C unreliable inconclusive 76 1d00h 979d 0/27 upstream: reported C repro on 2021/10/15 18:41
upstream INFO: rcu detected stall in sys_exit_group (6) mm C 4 1359d 1365d 19/27 fixed on 2021/03/10 01:48
linux-5.15 INFO: rcu detected stall in sys_exit_group (2) 3 64d 98d 0/3 upstream: reported on 2024/03/14 09:49
linux-6.1 INFO: rcu detected stall in sys_exit_group (3) origin:upstream C 7 12d 149d 0/3 upstream: reported C repro on 2024/01/23 11:05
linux-6.1 INFO: rcu detected stall in sys_exit_group (2) 1 296d 296d 0/3 auto-obsoleted due to no activity on 2023/12/07 20:57
linux-5.15 INFO: rcu detected stall in sys_exit_group 1 358d 358d 0/3 auto-obsoleted due to no activity on 2023/10/06 21:30
upstream INFO: rcu detected stall in sys_exit_group (2) cgroups mm 56 1660d 1662d 0/27 closed as invalid on 2019/12/04 14:14
upstream INFO: rcu detected stall in sys_exit_group (3) kernel 8 1626d 1626d 0/27 closed as invalid on 2020/01/08 05:23
upstream INFO: rcu detected stall in sys_exit_group (4) kernel 13 1625d 1626d 0/27 closed as invalid on 2020/01/09 08:13
upstream INFO: rcu detected stall in sys_exit_group (5) mm 1 1547d 1547d 0/27 auto-closed as invalid on 2020/06/25 07:58
upstream INFO: rcu detected stall in sys_exit_group kernel C done 1 1741d 1737d 13/27 fixed on 2019/10/09 10:54
android-5-15 BUG: soft lockup in sys_exit_group origin:downstream C 7 14d 74d 0/2 upstream: reported C repro on 2024/04/07 14:27

Sample crash report:
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P9338 1-...D } 2669 jiffies s: 20769 root: 0x2/T
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9748 Comm: syz-executor.3 Not tainted 6.1.27-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x60 kernel/kcov.c:203
Code: e8 25 00 00 00 0f 0b 0f 1f 00 53 48 89 fb e8 17 00 00 00 48 8b 3d a8 26 c9 0c 48 89 de 5b e9 d7 74 55 00 cc cc cc cc cc cc cc <48> 8b 04 24 65 48 8b 0d 74 a6 78 7e 65 8b 15 75 a6 78 7e f7 c2 00
RSP: 0018:ffffc900001e0d20 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000001 RCX: ffffffff817965c0
RDX: ffff88803c6c8000 RSI: ffffffff8b3cbf80 RDI: ffffffff8b3cbf40
RBP: 0000000000000001 R08: ffffffff817965e6 R09: fffffbfff1ca5da6
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: ffff8880b992a5c0 R14: ffff888075847340 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b33425000 CR3: 000000003756b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <IRQ>
 trace_hrtimer_start include/trace/events/timer.h:198 [inline]
 debug_activate kernel/time/hrtimer.c:476 [inline]
 enqueue_hrtimer+0xcd/0x390 kernel/time/hrtimer.c:1084
 __run_hrtimer kernel/time/hrtimer.c:1702 [inline]
 __hrtimer_run_queues+0x728/0xe50 kernel/time/hrtimer.c:1749
 hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
 local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1096 [inline]
 __sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1113
 sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1107
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:649
RIP: 0010:lock_release+0x637/0xa20 kernel/locking/lockdep.c:5693
Code: 3c 3b 00 74 08 4c 89 f7 e8 e6 15 76 00 f6 84 24 91 00 00 00 02 75 6f 41 f7 c5 00 02 00 00 74 01 fb 48 c7 44 24 60 0e 36 e0 45 <4b> c7 04 27 00 00 00 00 4b c7 44 27 08 00 00 00 00 65 48 8b 04 25
RSP: 0018:ffffc9000b13f580 EFLAGS: 00000206
RAX: 0000000000000001 RBX: 1ffff92001627ec2 RCX: ffffc9000b13f603
RDX: 0000000000000002 RSI: ffffffff8aebe1a0 RDI: ffffffff8b3cbfa0
RBP: ffffc9000b13f6b0 R08: dffffc0000000000 R09: fffffbfff1ca5da6
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001627ebc
R13: 0000000000000246 R14: ffffc9000b13f610 R15: dffffc0000000000
 page_remove_rmap+0x819/0xed0 mm/rmap.c:1462
 zap_pte_range mm/memory.c:1443 [inline]
 zap_pmd_range mm/memory.c:1564 [inline]
 zap_pud_range mm/memory.c:1593 [inline]
 zap_p4d_range mm/memory.c:1614 [inline]
 unmap_page_range+0x1217/0x2740 mm/memory.c:1635
 unmap_vmas+0x3c4/0x560 mm/memory.c:1720
 exit_mmap+0x252/0x9f0 mm/mmap.c:3127
 __mmput+0x115/0x3c0 kernel/fork.c:1191
 exit_mm+0x226/0x300 kernel/exit.c:563
 do_exit+0x67e/0x2300 kernel/exit.c:856
 do_group_exit+0x202/0x2b0 kernel/exit.c:1019
 __do_sys_exit_group kernel/exit.c:1030 [inline]
 __se_sys_exit_group kernel/exit.c:1028 [inline]
 __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fc5e7c8c169
Code: Unable to access opcode bytes at 0x7fc5e7c8c13f.
RSP: 002b:00007ffee078ac28 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 000000000000001e RCX: 00007fc5e7c8c169
RDX: 00007fc5e7c3e01b RSI: ffffffffffffffb8 RDI: 0000000000000000
RBP: 0000000000000001 R08: 0000000053b70bbc R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 0000000000000000 R14: 0000000000000001 R15: 00007ffee078ad10
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/05/10 22:23 linux-6.1.y ca48fc16c493 14b12a99 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: rcu detected stall in sys_exit_group
* Struck through repros no longer work on HEAD.