syzbot


INFO: task hung in synchronize_rcu

Status: internal: reported on 2025/07/11 21:20
Reported-by: syzbot+0232e02d8636b4ed7022@syzkaller.appspotmail.com
First crash: 71d, last: 2h34m
Similar bugs (13)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in synchronize_rcu (3) 1 C done done 374 931d 1868d 22/29 fixed on 2023/02/24 13:50
linux-6.1 INFO: task hung in synchronize_rcu origin:lts-only 1 C unreliable 20 5d08h 886d 0/3 upstream: reported C repro on 2023/04/01 04:49
android-49 INFO: task hung in synchronize_rcu 1 1 2104d 2104d 0/3 auto-closed as invalid on 2020/03/28 16:57
linux-4.14 INFO: task hung in synchronize_rcu vfs 1 C error 162 945d 2127d 0/1 upstream: reported C repro on 2019/11/07 04:32
linux-4.19 INFO: task hung in synchronize_rcu 1 C error 70 935d 2125d 0/1 upstream: reported C repro on 2019/11/08 21:27
linux-5.15 INFO: task hung in synchronize_rcu 1 1 871d 871d 0/3 auto-obsoleted due to no activity on 2023/08/14 02:05
linux-5.15 INFO: task hung in synchronize_rcu (3) origin:lts-only 1 C error 14 30d 404d 0/3 upstream: reported C repro on 2024/07/26 03:55
upstream INFO: task hung in synchronize_rcu 1 syz done 1206 2105d 2131d 14/29 fixed on 2019/11/29 15:48
upstream INFO: task hung in synchronize_rcu (4) fs net 1 C done error 907 22h08m 853d 0/29 upstream: reported C repro on 2023/05/04 02:01
linux-5.15 INFO: task hung in synchronize_rcu (2) 1 1 560d 560d 0/3 auto-obsoleted due to no activity on 2024/05/31 13:53
android-414 INFO: task hung in synchronize_rcu 1 1 2123d 2123d 0/1 auto-closed as invalid on 2020/03/10 10:42
upstream INFO: task hung in synchronize_rcu (2) trace 1 8 2103d 2104d 0/29 closed as invalid on 2019/11/30 16:54
upstream INFO: task hung in rtnetlink_rcv_msg net 1 C inconclusive inconclusive 1970 421d 2384d 26/29 fixed on 2024/07/09 19:14

Sample crash report:
INFO: task kworker/1:5:14769 blocked for more than 122 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:5     state:D stack:0     pid:14769 tgid:14769 ppid:2      flags:0x00004000
Workqueue: events xfrm_state_gc_task
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5945 [inline]
 __schedule+0x1322/0x1df0 kernel/sched/core.c:7791
 __schedule_loop kernel/sched/core.c:7872 [inline]
 schedule+0xc6/0x240 kernel/sched/core.c:7887
 schedule_timeout+0xb2/0x3a0 kernel/time/timer.c:2595
 do_wait_for_common kernel/sched/completion.c:95 [inline]
 __wait_for_common kernel/sched/completion.c:116 [inline]
 wait_for_common+0x359/0x630 kernel/sched/completion.c:127
 wait_for_completion_state+0x19/0x40 kernel/sched/completion.c:264
 __wait_rcu_gp+0x296/0x2c0 kernel/rcu/update.c:514
 synchronize_rcu_normal+0x113/0x160 kernel/rcu/tree.c:4043
 synchronize_rcu+0x98/0x2e0 kernel/rcu/tree.c:4121
 xfrm_state_gc_task+0xca/0x170 net/xfrm/xfrm_state.c:569
 process_one_work kernel/workqueue.c:3238 [inline]
 process_scheduled_works+0x7d5/0x1020 kernel/workqueue.c:3319
 worker_thread+0xc58/0x1250 kernel/workqueue.c:3400
 kthread+0x2c7/0x370 kernel/kthread.c:389
 ret_from_fork+0x64/0xa0 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 37 Comm: khungtaskd Not tainted syzkaller #0 6e508aa732f414f9d300b832ff15c50b3cf7cfdc
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 __dump_stack+0x21/0x30 lib/dump_stack.c:94
 dump_stack_lvl+0x10c/0x190 lib/dump_stack.c:120
 dump_stack+0x19/0x20 lib/dump_stack.c:129
 nmi_cpu_backtrace+0x2bf/0x2d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x142/0x2c0 lib/nmi_backtrace.c:62
 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:41
 trigger_all_cpu_backtrace include/linux/nmi.h:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:267 [inline]
 watchdog+0xd8f/0xed0 kernel/hung_task.c:423
 kthread+0x2c7/0x370 kernel/kthread.c:389
 ret_from_fork+0x64/0xa0 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 33 Comm: rcuop/1 Not tainted syzkaller #0 6e508aa732f414f9d300b832ff15c50b3cf7cfdc
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:check_kcov_mode kernel/kcov.c:183 [inline]
RIP: 0010:write_comp_data kernel/kcov.c:246 [inline]
RIP: 0010:__sanitizer_cov_trace_const_cmp2+0x24/0x90 kernel/kcov.c:307
Code: 90 90 90 90 90 90 f3 0f 1e fa 55 48 89 e5 48 8b 45 08 65 48 8b 14 25 00 eb 04 00 65 8b 0d 3c 03 7f 7e 81 e1 00 01 ff 00 74 11 <81> f9 00 01 00 00 75 5b 83 ba ec 0b 00 00 00 74 52 8b 8a c8 0b 00
RSP: 0018:ffffc90000230750 EFLAGS: 00000206
RAX: ffffffff84ffea48 RBX: 0000000000000002 RCX: 0000000000000100
RDX: ffff888103679300 RSI: 0000000000000002 RDI: 000000000000ffff
RBP: ffffc90000230750 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffff520000460a0 R12: 00000000ffffffff
R13: ffff888108b99000 R14: ffff88814e28fb40 R15: 1ffff920000460fc
FS:  0000000000000000(0000) GS:ffff8881f6f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f89008f7d60 CR3: 000000010bb98000 CR4: 00000000003526b0
Call Trace:
 <IRQ>
 skb_mac_header_was_set include/linux/skbuff.h:3028 [inline]
 skb_mac_header include/linux/skbuff.h:3033 [inline]
 eth_hdr include/linux/if_ether.h:24 [inline]
 br_handle_frame_finish+0x4d8/0x1720 net/bridge/br_input.c:148
 nf_hook_bridge_pre net/bridge/br_input.c:301 [inline]
 br_handle_frame+0x5a6/0xba0 net/bridge/br_input.c:424
 __netif_receive_skb_core+0xf48/0x3940 net/core/dev.c:5651
 __netif_receive_skb_one_core net/core/dev.c:5755 [inline]
 __netif_receive_skb net/core/dev.c:5870 [inline]
 process_backlog+0x3e5/0xae0 net/core/dev.c:6206
 __napi_poll+0xd3/0x610 net/core/dev.c:6857
 napi_poll net/core/dev.c:6926 [inline]
 net_rx_action+0x584/0xce0 net/core/dev.c:7048
 handle_softirqs+0x1ab/0x630 kernel/softirq.c:621
 __do_softirq+0xf/0x16 kernel/softirq.c:659
 do_softirq+0xa6/0x100 kernel/softirq.c:503
 </IRQ>
 <TASK>
 __local_bh_enable_ip+0x74/0x80 kernel/softirq.c:430
 local_bh_enable include/linux/bottom_half.h:33 [inline]
 rcu_do_batch+0x5c6/0xd20 kernel/rcu/tree.c:2594
 nocb_cb_wait kernel/rcu/tree_nocb.h:923 [inline]
 rcu_nocb_cb_kthread+0x4dc/0xac0 kernel/rcu/tree_nocb.h:957
 kthread+0x2c7/0x370 kernel/kthread.c:389
 ret_from_fork+0x64/0xa0 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
net_ratelimit: 98110 callbacks suppressed
bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
net_ratelimit: 110731 callbacks suppressed
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:1b, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on bridge_slave_0 with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:26:1f:78:58:7c:37, vlan:0)
bridge0: received packet on veth0_to_bridge with own address as source address (addr:aa:aa:aa:aa:aa:0c, vlan:0)

Crashes (29):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/03 13:02 android16-6.12 53e4390f692f 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/09/03 07:03 android16-6.12 4ae522d0f966 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/09/03 00:41 android16-6.12 4ae522d0f966 96a211bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/31 15:49 android16-6.12 6879524e1c5a 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/29 14:23 android16-6.12 cbb0a15dcc1e 3e1beec6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/28 20:00 android16-6.12 cbb0a15dcc1e d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/28 02:44 android16-6.12 c17d1926681a e12e5ba4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/10 15:52 android16-6.12 d0c633175c04 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/08 08:40 android16-6.12 209015b548fb 6a893178 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/06 04:02 android16-6.12 78c6c49396da ffe1dd46 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/02 02:42 android16-6.12 bf0fb8bb181b 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/08/01 23:52 android16-6.12 bf0fb8bb181b 7368264b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/27 13:59 android16-6.12 e9bbc29c066a fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/23 16:19 android16-6.12 fc2476d0896a e1dd4f22 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/22 07:02 android16-6.12 2199f5c4b596 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/22 06:27 android16-6.12 2199f5c4b596 1555463b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/22 00:07 android16-6.12 25f19cb85021 56d87229 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/15 19:24 android16-6.12 603af016e4a8 03fcfc4b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/12 20:23 android16-6.12 21ed84930c16 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/12 13:03 android16-6.12 21ed84930c16 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/11 00:05 android16-6.12 8ea40f524391 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/10 10:32 android16-6.12 d893caf112c8 956bd956 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/08 17:41 android16-6.12 15d2fe054444 4d9fdfa4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/08 10:31 android16-6.12 f6ca783ba264 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/07 00:11 android16-6.12 e2bf362ee23b 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/04 17:24 android16-6.12 e2bf362ee23b d869b261 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/03 23:49 android16-6.12 e2bf362ee23b 76ad128c .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/07/02 06:25 android16-6.12 c40c54e66959 bc80e4f0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
2025/06/24 05:10 android16-6.12 1d4f4d446dbd e2f27c35 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-6-12-rust INFO: task hung in synchronize_rcu
* Struck through repros no longer work on HEAD.