[v5.15] INFO: task hung in ntfs_fallocate
0 views
Skip to first unread message
syzbot
5:08 AM (5 hours ago) 5:08 AM
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d3599a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=03096c353c6b825ff816
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/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03096c...@syzkaller.appspotmail.com
INFO: task syz.0.102:4782 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.102 state:D stack:29088 pid: 4782 ppid: 4181 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
vfs_fallocate+0x587/0x6f0 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:337
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff934f24749
RSP: 002b:00007ff93316a038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007ff93517b090 RCX: 00007ff934f24749
RDX: 000000000000000a RSI: 0000000000000001 RDI: 0000000000000007
RBP: 00007ff934fa8f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000009 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff93517b128 R14: 00007ff93517b090 R15: 00007fff4aa759b8
</TASK>
Showing all locks held in the system:
5 locks held by ksoftirqd/0/14:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3948:
#0: ffff88802ca53098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
2 locks held by syz-executor/4189:
#0: ffff888020000518 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
#1: ffff8881473c5468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2071
4 locks held by kworker/u4:13/4385:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000344fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d226b10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#3: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
3 locks held by syz.0.102/4749:
2 locks held by syz.0.102/4782:
#0: ffff88805ba54460 (sb_writers#21){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805ba54460 (sb_writers#21){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805d8e7240 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805d8e7240 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
2 locks held by kworker/0:16/6528:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003fefd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by syz.1.728/7415:
3 locks held by kworker/u4:15/7461:
1 lock held by syz.4.737/7487:
#0: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#0: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 1
CPU: 1 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/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 6521 Comm: kworker/0:13 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events_power_efficient wg_ratelimiter_gc_entries
RIP: 0010:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:205
Code: 84 00 00 00 00 00 53 48 89 fb e8 17 00 00 00 48 8b 3d d0 6b f1 0b 48 89 de 5b e9 d7 9e 43 00 00 00 cc cc 00 00 cc 48 8b 04 24 <65> 48 8b 0d a4 a3 8a 7e 65 8b 15 a5 a3 8a 7e 81 e2 00 01 ff 00 74
RSP: 0018:ffffc90000006d18 EFLAGS: 00000246
RAX: ffffffff8848fde0 RBX: 0000000000000001 RCX: ffff8880199f3b80
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000100007f R08: ffff8880199f3b80 R09: 0000000000000003
R10: 0000000000000005 R11: 0000000000000100 R12: ffffc90000006f80
R13: dffffc0000000000 R14: 0000000000000002 R15: ffff888022250000
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f86871fead8 CR3: 0000000021107000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__mkroute_output net/ipv4/route.c:2606 [inline]
ip_route_output_key_hash_rcu+0x1420/0x24d0 net/ipv4/route.c:2854
ip_route_output_key_hash+0x1b1/0x2e0 net/ipv4/route.c:2683
__ip_route_output_key include/net/route.h:126 [inline]
ip_route_output_flow+0x26/0x150 net/ipv4/route.c:2913
ip_route_output_key include/net/route.h:142 [inline]
ip_route_me_harder+0x5d6/0xf10 net/ipv4/netfilter.c:53
synproxy_send_tcp+0x372/0x6d0 net/netfilter/nf_synproxy_core.c:453
synproxy_send_client_synack+0x886/0xdd0 net/netfilter/nf_synproxy_core.c:506
nft_synproxy_eval_v4+0x36b/0x560 net/netfilter/nft_synproxy.c:59
nft_synproxy_do_eval+0x341/0x570 net/netfilter/nft_synproxy.c:141
expr_call_ops_eval net/netfilter/nf_tables_core.c:198 [inline]
nft_do_chain+0x3fc/0x1420 net/netfilter/nf_tables_core.c:238
nft_do_chain_inet+0x22b/0x300 net/netfilter/nft_chain_filter.c:161
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_slow+0xb9/0x200 net/netfilter/core.c:584
nf_hook include/linux/netfilter.h:257 [inline]
NF_HOOK+0x1cb/0x360 include/linux/netfilter.h:300
NF_HOOK+0x2d6/0x360 include/linux/netfilter.h:302
__netif_receive_skb_one_core net/core/dev.c:5525 [inline]
__netif_receive_skb+0xcc/0x290 net/core/dev.c:5639
process_backlog+0x364/0x780 net/core/dev.c:6516
__napi_poll+0xc0/0x430 net/core/dev.c:7075
napi_poll net/core/dev.c:7142 [inline]
net_rx_action+0x4a8/0x9c0 net/core/dev.c:7232
handle_softirqs+0x328/0x820 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:lock_acquire+0x6/0x3f0 kernel/locking/lockdep.c:5591
Code: e9 35 fb ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 65 8b 05 e1 75 a6 7e a9 00 ff ff 00 0f 95 c0 c3 55 48 89 e5 41 57 <41> 56 41 55 41 54 53 48 83 e4 e0 48 81 ec e0 00 00 00 4c 89 4c 24
RSP: 0018:ffffc90002f5fbb8 EFLAGS: 00000246
RAX: 1ffff1100333ea0d RBX: ffffffff8ca60960 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8ca60978
RBP: ffffc90002f5fbc0 R08: 0000000000000001 R09: 0000000000000000
R10: fffffbfff194c12d R11: 1ffffffff194c12c R12: ffff888061eb3e78
R13: ffff888024540418 R14: 00000000000007d0 R15: ffffffffffffffa0
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:364 [inline]
wg_ratelimiter_gc_entries+0x59/0x450 drivers/net/wireguard/ratelimiter.c:63
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=15d3599a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=03096c353c6b825ff816
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/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03096c...@syzkaller.appspotmail.com
INFO: task syz.0.102:4782 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.102 state:D stack:29088 pid: 4782 ppid: 4181 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
vfs_fallocate+0x587/0x6f0 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:337
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff934f24749
RSP: 002b:00007ff93316a038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007ff93517b090 RCX: 00007ff934f24749
RDX: 000000000000000a RSI: 0000000000000001 RDI: 0000000000000007
RBP: 00007ff934fa8f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000009 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff93517b128 R14: 00007ff93517b090 R15: 00007fff4aa759b8
</TASK>
Showing all locks held in the system:
5 locks held by ksoftirqd/0/14:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3948:
#0: ffff88802ca53098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
2 locks held by syz-executor/4189:
#0: ffff888020000518 (&disk->open_mutex){+.+.}-{3:3}, at: blkdev_put+0xf9/0x7d0 block/bdev.c:915
#1: ffff8881473c5468 (&lo->lo_mutex){+.+.}-{3:3}, at: lo_release+0x4d/0x1f0 drivers/block/loop.c:2071
4 locks held by kworker/u4:13/4385:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000344fd00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d226b10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#3: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x347/0x6b0 kernel/rcu/tree_exp.h:845
3 locks held by syz.0.102/4749:
2 locks held by syz.0.102/4782:
#0: ffff88805ba54460 (sb_writers#21){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805ba54460 (sb_writers#21){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805d8e7240 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805d8e7240 (&sb->s_type->i_mutex_key#30){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
2 locks held by kworker/0:16/6528:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90003fefd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
2 locks held by syz.1.728/7415:
3 locks held by kworker/u4:15/7461:
1 lock held by syz.4.737/7487:
#0: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#0: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
=============================================
NMI backtrace for cpu 1
CPU: 1 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/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 6521 Comm: kworker/0:13 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events_power_efficient wg_ratelimiter_gc_entries
RIP: 0010:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:205
Code: 84 00 00 00 00 00 53 48 89 fb e8 17 00 00 00 48 8b 3d d0 6b f1 0b 48 89 de 5b e9 d7 9e 43 00 00 00 cc cc 00 00 cc 48 8b 04 24 <65> 48 8b 0d a4 a3 8a 7e 65 8b 15 a5 a3 8a 7e 81 e2 00 01 ff 00 74
RSP: 0018:ffffc90000006d18 EFLAGS: 00000246
RAX: ffffffff8848fde0 RBX: 0000000000000001 RCX: ffff8880199f3b80
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 000000000100007f R08: ffff8880199f3b80 R09: 0000000000000003
R10: 0000000000000005 R11: 0000000000000100 R12: ffffc90000006f80
R13: dffffc0000000000 R14: 0000000000000002 R15: ffff888022250000
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f86871fead8 CR3: 0000000021107000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__mkroute_output net/ipv4/route.c:2606 [inline]
ip_route_output_key_hash_rcu+0x1420/0x24d0 net/ipv4/route.c:2854
ip_route_output_key_hash+0x1b1/0x2e0 net/ipv4/route.c:2683
__ip_route_output_key include/net/route.h:126 [inline]
ip_route_output_flow+0x26/0x150 net/ipv4/route.c:2913
ip_route_output_key include/net/route.h:142 [inline]
ip_route_me_harder+0x5d6/0xf10 net/ipv4/netfilter.c:53
synproxy_send_tcp+0x372/0x6d0 net/netfilter/nf_synproxy_core.c:453
synproxy_send_client_synack+0x886/0xdd0 net/netfilter/nf_synproxy_core.c:506
nft_synproxy_eval_v4+0x36b/0x560 net/netfilter/nft_synproxy.c:59
nft_synproxy_do_eval+0x341/0x570 net/netfilter/nft_synproxy.c:141
expr_call_ops_eval net/netfilter/nf_tables_core.c:198 [inline]
nft_do_chain+0x3fc/0x1420 net/netfilter/nf_tables_core.c:238
nft_do_chain_inet+0x22b/0x300 net/netfilter/nft_chain_filter.c:161
nf_hook_entry_hookfn include/linux/netfilter.h:142 [inline]
nf_hook_slow+0xb9/0x200 net/netfilter/core.c:584
nf_hook include/linux/netfilter.h:257 [inline]
NF_HOOK+0x1cb/0x360 include/linux/netfilter.h:300
NF_HOOK+0x2d6/0x360 include/linux/netfilter.h:302
__netif_receive_skb_one_core net/core/dev.c:5525 [inline]
__netif_receive_skb+0xcc/0x290 net/core/dev.c:5639
process_backlog+0x364/0x780 net/core/dev.c:6516
__napi_poll+0xc0/0x430 net/core/dev.c:7075
napi_poll net/core/dev.c:7142 [inline]
net_rx_action+0x4a8/0x9c0 net/core/dev.c:7232
handle_softirqs+0x328/0x820 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:lock_acquire+0x6/0x3f0 kernel/locking/lockdep.c:5591
Code: e9 35 fb ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 65 8b 05 e1 75 a6 7e a9 00 ff ff 00 0f 95 c0 c3 55 48 89 e5 41 57 <41> 56 41 55 41 54 53 48 83 e4 e0 48 81 ec e0 00 00 00 4c 89 4c 24
RSP: 0018:ffffc90002f5fbb8 EFLAGS: 00000246
RAX: 1ffff1100333ea0d RBX: ffffffff8ca60960 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8ca60978
RBP: ffffc90002f5fbc0 R08: 0000000000000001 R09: 0000000000000000
R10: fffffbfff194c12d R11: 1ffffffff194c12c R12: ffff888061eb3e78
R13: ffff888024540418 R14: 00000000000007d0 R15: ffffffffffffffa0
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:364 [inline]
wg_ratelimiter_gc_entries+0x59/0x450 drivers/net/wireguard/ratelimiter.c:63
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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
8:56 AM (1 hour ago) 8:56 AM
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=141c95fa580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11aa85fc580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/b9fbf2b681e0/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03096c...@syzkaller.appspotmail.com
INFO: task syz.0.17:4352 blocked for more than 143 seconds.
RSP: 002b:00007ff765731038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007ff76633a090 RCX: 00007ff7660e3749
RDX: 000000000000000a RSI: 0000000000000001 RDI: 0000000000000006
RBP: 00007ff766167f91 R08: 0000000000000000 R09: 0000000000000000
#0: ffff88802ba54098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
2 locks held by syz.0.17/4352:
#0: ffff88807be24460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88807be24460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb03a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb03a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
3 locks held by syz.1.18/4376:
2 locks held by syz.1.18/4378:
#0: ffff88801a396460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88801a396460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb79a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb79a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.2.19/4408:
2 locks held by syz.2.19/4409:
#0: ffff888025000460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff888025000460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef2f240 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef2f240 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.3.20/4430:
2 locks held by syz.3.20/4431:
#0: ffff88801a7e4460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88801a7e4460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805ccfeae0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805ccfeae0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.4.21/4461:
2 locks held by syz.4.21/4462:
#0: ffff888075186460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff888075186460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb3740 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb3740 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
3 locks held by syz.5.22/4497:
2 locks held by syz.5.22/4498:
#0: ffff88805cb00460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805cb00460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef51260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef51260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.6.23/4528:
2 locks held by syz.6.23/4529:
#0: ffff88805b1b4460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805b1b4460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb1260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb1260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.7.24/4563:
2 locks held by syz.7.24/4564:
#0: ffff88807bbf8460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88807bbf8460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef54600 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef54600 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
=============================================
NMI backtrace for cpu 1
CPU: 1 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/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4351 Comm: syz.0.17 Not tainted syzkaller #0
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:331 [inline]
RIP: 0010:rcu_is_watching+0x56/0xa0 kernel/rcu/tree.c:1123
Code: f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 40 83 58 00 48 c7 c3 08 b3 03 00 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 <84> c0 75 2b 8b 03 65 ff 0d 35 be 9e 7e 74 08 24 01 5b 41 5e 41 5f
RSP: 0018:ffffc9000308f700 EFLAGS: 00000a02
RAX: 0000000000000000 RBX: ffff8880b903b308 RCX: 2576037c3ff0f300
RDX: 0000000000000000 RSI: ffffffff8a59e7e0 RDI: ffffffff8a59e7a0
RBP: ffffc9000308f830 R08: dffffc0000000000 R09: fffffbfff1ad26b6
R10: fffffbfff1ad26b6 R11: 1ffffffff1ad26b5 R12: ffff88805cdb01b0
R13: 1ffff92000611ef0 R14: ffffffff8bbc0820 R15: dffffc0000000000
FS: 00007ff7657526c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0xcd/0x3f0 kernel/locking/lockdep.c:5594
down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
attr_data_get_block+0x10d/0x1880 fs/ntfs3/attrib.c:831
ntfs_compress_write+0x6fe/0x1c30 fs/ntfs3/file.c:929
ntfs_file_write_iter+0x3d7/0x590 fs/ntfs3/file.c:1146
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff765752038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff766339fa0 RCX: 00007ff7660e3749
RDX: 0000000000000020 RSI: 0000200000000980 RDI: 0000000000000006
RBP: 00007ff766167f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff76633a038 R14: 00007ff766339fa0 R15: 00007fff274ae3b8
</TASK>
---
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.
HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=03096c353c6b825ff816
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159c059a580000
dashboard link: https://syzkaller.appspot.com/bug?extid=03096c353c6b825ff816
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11aa85fc580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+03096c...@syzkaller.appspotmail.com
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.17 state:D stack:29008 pid: 4352 ppid: 4294 flags:0x00004004
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
vfs_fallocate+0x587/0x6f0 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:337
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff7660e3749
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
vfs_fallocate+0x587/0x6f0 fs/open.c:308
ksys_fallocate fs/open.c:331 [inline]
__do_sys_fallocate fs/open.c:339 [inline]
__se_sys_fallocate fs/open.c:337 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:337
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RSP: 002b:00007ff765731038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007ff76633a090 RCX: 00007ff7660e3749
RDX: 000000000000000a RSI: 0000000000000001 RDI: 0000000000000006
RBP: 00007ff766167f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000009 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff76633a128 R14: 00007ff76633a090 R15: 00007fff274ae3b8
</TASK>
Showing all locks held in the system:
2 locks held by kworker/u4:0/9:
Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by getty/3945:
#0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
#0: ffff88802ba54098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
4 locks held by syz.0.17/4351:
2 locks held by syz.0.17/4352:
#0: ffff88807be24460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88807be24460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb03a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb03a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
3 locks held by syz.1.18/4376:
2 locks held by syz.1.18/4378:
#0: ffff88801a396460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88801a396460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb79a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb79a0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.2.19/4408:
2 locks held by syz.2.19/4409:
#0: ffff888025000460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff888025000460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef2f240 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef2f240 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.3.20/4430:
2 locks held by syz.3.20/4431:
#0: ffff88801a7e4460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88801a7e4460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805ccfeae0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805ccfeae0 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.4.21/4461:
2 locks held by syz.4.21/4462:
#0: ffff888075186460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff888075186460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb3740 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb3740 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
3 locks held by syz.5.22/4497:
2 locks held by syz.5.22/4498:
#0: ffff88805cb00460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805cb00460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef51260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef51260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.6.23/4528:
2 locks held by syz.6.23/4529:
#0: ffff88805b1b4460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88805b1b4460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88805cdb1260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805cdb1260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
4 locks held by syz.7.24/4563:
2 locks held by syz.7.24/4564:
#0: ffff88807bbf8460 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3043 [inline]
#0: ffff88807bbf8460 (sb_writers#13){.+.+}-{0:0}, at: vfs_fallocate+0x4f4/0x6f0 fs/open.c:307
#1: ffff88806ef54600 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88806ef54600 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: ntfs_fallocate+0x1a9/0xcc0 fs/ntfs3/file.c:558
=============================================
NMI backtrace for cpu 1
CPU: 1 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/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:arch_atomic_read arch/x86/include/asm/atomic.h:29 [inline]
RIP: 0010:rcu_dynticks_curr_cpu_in_eqs kernel/rcu/tree.c:331 [inline]
RIP: 0010:rcu_is_watching+0x56/0xa0 kernel/rcu/tree.c:1123
Code: f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 40 83 58 00 48 c7 c3 08 b3 03 00 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 <84> c0 75 2b 8b 03 65 ff 0d 35 be 9e 7e 74 08 24 01 5b 41 5e 41 5f
RSP: 0018:ffffc9000308f700 EFLAGS: 00000a02
RAX: 0000000000000000 RBX: ffff8880b903b308 RCX: 2576037c3ff0f300
RDX: 0000000000000000 RSI: ffffffff8a59e7e0 RDI: ffffffff8a59e7a0
RBP: ffffc9000308f830 R08: dffffc0000000000 R09: fffffbfff1ad26b6
R10: fffffbfff1ad26b6 R11: 1ffffffff1ad26b5 R12: ffff88805cdb01b0
R13: 1ffff92000611ef0 R14: ffffffff8bbc0820 R15: dffffc0000000000
FS: 00007ff7657526c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bffcdbca38 CR3: 00000000753a4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
trace_lock_acquire include/trace/events/lock.h:13 [inline]
lock_acquire+0xcd/0x3f0 kernel/locking/lockdep.c:5594
down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
attr_data_get_block+0x10d/0x1880 fs/ntfs3/attrib.c:831
ntfs_compress_write+0x6fe/0x1c30 fs/ntfs3/file.c:929
ntfs_file_write_iter+0x3d7/0x590 fs/ntfs3/file.c:1146
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff7660e3749
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff765752038 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007ff766339fa0 RCX: 00007ff7660e3749
RDX: 0000000000000020 RSI: 0000200000000980 RDI: 0000000000000006
RBP: 00007ff766167f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff76633a038 R14: 00007ff766339fa0 R15: 00007fff274ae3b8
</TASK>
---
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.
Reply all
Reply to author
Forward
0 new messages