[v6.1] INFO: task hung in nilfs_segctor_thread (2)
0 views
Skip to first unread message
syzbot
Jan 6, 2026, 2:57:21 AM (3 days ago) Jan 6
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12fb7efc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=6f213c09daa0f93dfeb8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/50ceb00b1b39/disk-50cbba13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ebb8883b9a29/vmlinux-50cbba13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7edc2a795f03/bzImage-50cbba13.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6f213c...@syzkaller.appspotmail.com
INFO: task segctord:5995 blocked for more than 156 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:segctord state:D stack:28912 pid:5995 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x10ec/0x40b0 kernel/sched/core.c:6561
schedule+0xb9/0x180 kernel/sched/core.c:6637
rwsem_down_write_slowpath+0xbed/0x1090 kernel/locking/rwsem.c:1189
nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2560 [inline]
nilfs_segctor_thread+0x4e8/0xff0 fs/nilfs2/segment.c:2645
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Showing all locks held in the system:
3 locks held by kworker/0:0/7:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900000c7d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888056095240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x26b/0x32b0 drivers/net/netdevsim/fib.c:1491
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8c92bab0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8c92c2d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by kworker/1:1/41:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90000b27d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
2 locks held by kworker/1:2/951:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc9000469fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
2 locks held by getty/4026:
#0: ffff88814d107098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41b/0x1380 drivers/tty/n_tty.c:2198
5 locks held by kworker/1:5/4327:
2 locks held by kworker/1:9/4392:
5 locks held by kworker/u4:8/4526:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90004d47d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffffffff8db2e6d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:594
#3: ffff888041d513e8 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_destruct+0x112/0x300 drivers/net/wireguard/device.c:249
#4: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#4: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x346/0x830 kernel/rcu/tree_exp.h:962
4 locks held by kworker/u4:9/4527:
3 locks held by kworker/0:7/5087:
2 locks held by dhcpcd/5582:
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1400
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x346/0x830 kernel/rcu/tree_exp.h:962
2 locks held by syz.5.284/5993:
1 lock held by segctord/5995:
#0: ffff888079b622a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
3 locks held by kworker/0:18/6435:
3 locks held by kworker/0:20/6437:
3 locks held by syz-executor/6961:
#0: ffff888068ac10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888068ac10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888068ac0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz-executor/7000:
#0: ffff8880751b90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880751b90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880751b8078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.7.361/7175:
#0: ffff888077ae90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888077ae90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888077ae8078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
1 lock held by rm/7195:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3f4/0x470 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4357 Comm: kworker/u4:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: phy26 ieee80211_iface_work
RIP: 0010:ieee80211_rx_bss_info net/mac80211/ibss.c:1114 [inline]
RIP: 0010:ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1609 [inline]
RIP: 0010:ieee80211_ibss_rx_queued_mgmt+0x453/0x2b10 net/mac80211/ibss.c:1638
Code: 06 89 84 24 a4 00 00 00 48 89 54 24 48 4c 8d 7a 40 4c 89 f8 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 ff e8 10 48 45 f8 4d 8b 3f <48> 8b 44 24 28 4c 8d 60 44 4c 89 e0 48 c1 e8 03 48 b9 00 00 00 00
RSP: 0018:ffffc900046af8e0 EFLAGS: 00000246
RAX: 1ffff110067961d8 RBX: 1ffff1100ae5b2b5 RCX: ffff88802f57d940
RDX: ffff888033cb0e80 RSI: ffff8880177c7ccc RDI: 0000000000000000
RBP: ffffc900046afbb8 R08: dffffc0000000000 R09: fffff520008d5ecc
R10: fffff520008d5ecc R11: 1ffff920008d5ecb R12: dffffc0000000000
R13: ffff8880572d9af8 R14: 1ffff11002ef8f99 R15: ffff888033cb0760
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff8a08f1fe8 CR3: 000000000c68e000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_iface_process_skb net/mac80211/iface.c:1679 [inline]
ieee80211_iface_work+0x726/0xc80 net/mac80211/iface.c:1733
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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
syzbot found the following issue on:
HEAD commit: 50cbba13faa2 Linux 6.1.159
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12fb7efc580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a5cbd268406bf43
dashboard link: https://syzkaller.appspot.com/bug?extid=6f213c09daa0f93dfeb8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/50ceb00b1b39/disk-50cbba13.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ebb8883b9a29/vmlinux-50cbba13.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7edc2a795f03/bzImage-50cbba13.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+6f213c...@syzkaller.appspotmail.com
INFO: task segctord:5995 blocked for more than 156 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:segctord state:D stack:28912 pid:5995 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x10ec/0x40b0 kernel/sched/core.c:6561
schedule+0xb9/0x180 kernel/sched/core.c:6637
rwsem_down_write_slowpath+0xbed/0x1090 kernel/locking/rwsem.c:1189
nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2560 [inline]
nilfs_segctor_thread+0x4e8/0xff0 fs/nilfs2/segment.c:2645
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Showing all locks held in the system:
3 locks held by kworker/0:0/7:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900000c7d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888056095240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x26b/0x32b0 drivers/net/netdevsim/fib.c:1491
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8c92bab0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8c92c2d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8c92b120 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by kworker/1:1/41:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90000b27d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
2 locks held by kworker/1:2/951:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc9000469fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
2 locks held by getty/4026:
#0: ffff88814d107098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41b/0x1380 drivers/tty/n_tty.c:2198
5 locks held by kworker/1:5/4327:
2 locks held by kworker/1:9/4392:
5 locks held by kworker/u4:8/4526:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90004d47d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffffffff8db2e6d0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:594
#3: ffff888041d513e8 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_destruct+0x112/0x300 drivers/net/wireguard/device.c:249
#4: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#4: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x346/0x830 kernel/rcu/tree_exp.h:962
4 locks held by kworker/u4:9/4527:
3 locks held by kworker/0:7/5087:
2 locks held by dhcpcd/5582:
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:653 [inline]
#0: ffff888073300810 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1400
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#1: ffffffff8c930df8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x346/0x830 kernel/rcu/tree_exp.h:962
2 locks held by syz.5.284/5993:
1 lock held by segctord/5995:
#0: ffff888079b622a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x252/0x4c0 fs/nilfs2/segment.c:357
3 locks held by kworker/0:18/6435:
3 locks held by kworker/0:20/6437:
3 locks held by syz-executor/6961:
#0: ffff888068ac10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888068ac10b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888068ac0078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz-executor/7000:
#0: ffff8880751b90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff8880751b90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff8880751b8078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
3 locks held by syz.7.361/7175:
#0: ffff888077ae90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close net/bluetooth/hci_core.c:508 [inline]
#0: ffff888077ae90b8 (&hdev->req_lock){+.+.}-{3:3}, at: hci_unregister_dev+0x1fa/0x4f0 net/bluetooth/hci_core.c:2705
#1: ffff888077ae8078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_close_sync+0x458/0xf40 net/bluetooth/hci_sync.c:5233
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1826 [inline]
#2: ffffffff8dc98f48 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xac/0x290 net/bluetooth/hci_conn.c:2504
1 lock held by rm/7195:
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3f4/0x470 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4357 Comm: kworker/u4:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: phy26 ieee80211_iface_work
RIP: 0010:ieee80211_rx_bss_info net/mac80211/ibss.c:1114 [inline]
RIP: 0010:ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1609 [inline]
RIP: 0010:ieee80211_ibss_rx_queued_mgmt+0x453/0x2b10 net/mac80211/ibss.c:1638
Code: 06 89 84 24 a4 00 00 00 48 89 54 24 48 4c 8d 7a 40 4c 89 f8 48 c1 e8 03 42 80 3c 20 00 74 08 4c 89 ff e8 10 48 45 f8 4d 8b 3f <48> 8b 44 24 28 4c 8d 60 44 4c 89 e0 48 c1 e8 03 48 b9 00 00 00 00
RSP: 0018:ffffc900046af8e0 EFLAGS: 00000246
RAX: 1ffff110067961d8 RBX: 1ffff1100ae5b2b5 RCX: ffff88802f57d940
RDX: ffff888033cb0e80 RSI: ffff8880177c7ccc RDI: 0000000000000000
RBP: ffffc900046afbb8 R08: dffffc0000000000 R09: fffff520008d5ecc
R10: fffff520008d5ecc R11: 1ffff920008d5ecb R12: dffffc0000000000
R13: ffff8880572d9af8 R14: 1ffff11002ef8f99 R15: ffff888033cb0760
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff8a08f1fe8 CR3: 000000000c68e000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ieee80211_iface_process_skb net/mac80211/iface.c:1679 [inline]
ieee80211_iface_work+0x726/0xc80 net/mac80211/iface.c:1733
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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