syzbot


INFO: task hung in f2fs_file_write_iter

Status: upstream: reported on 2022/11/20 07:00
Subsystems: f2fs
[Documentation on labels]
Reported-by: syzbot+656e8503e4a4f31ebf36@syzkaller.appspotmail.com
First crash: 571d, last: 467d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in f2fs_file_write_iter f2fs 5 370d 467d 0/28 auto-obsoleted due to no activity on 2023/09/06 20:28
upstream INFO: task hung in f2fs_file_write_iter (2) f2fs 1 209d 209d 0/28 auto-obsoleted due to no activity on 2024/02/14 19:21

Sample crash report:
F2FS-fs (loop5): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 24
F2FS-fs (loop5): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 24
F2FS-fs (loop5): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 24
INFO: task syz-executor.5:12267 blocked for more than 140 seconds.
      Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5  D24600 12267   8135 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2828 [inline]
 __schedule+0x887/0x2040 kernel/sched/core.c:3517
 schedule+0x8d/0x1b0 kernel/sched/core.c:3561
 __rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:589 [inline]
 rwsem_down_write_failed+0x3aa/0x760 kernel/locking/rwsem-xadd.c:618
 call_rwsem_down_write_failed+0x13/0x20 arch/x86/lib/rwsem.S:117
 __down_write arch/x86/include/asm/rwsem.h:142 [inline]
 down_write+0x4f/0x90 kernel/locking/rwsem.c:72
 inode_lock include/linux/fs.h:748 [inline]
 f2fs_file_write_iter+0x218/0xbe0 fs/f2fs/file.c:2996
 call_write_iter include/linux/fs.h:1821 [inline]
 do_iter_readv_writev+0x668/0x790 fs/read_write.c:681
 do_iter_write+0x182/0x5d0 fs/read_write.c:960
 vfs_iter_write+0x70/0xa0 fs/read_write.c:973
 iter_file_splice_write+0x60d/0xbb0 fs/splice.c:750
 do_splice_from fs/splice.c:852 [inline]
 direct_splice_actor+0x115/0x160 fs/splice.c:1025
 splice_direct_to_actor+0x33f/0x8d0 fs/splice.c:980
 do_splice_direct+0x1a7/0x270 fs/splice.c:1068
 do_sendfile+0x550/0xc30 fs/read_write.c:1447
 __do_sys_sendfile64 fs/read_write.c:1508 [inline]
 __se_sys_sendfile64+0x147/0x160 fs/read_write.c:1494
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f86c91890f9
Code: Bad RIP value.
RSP: 002b:00007f86c76da168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007f86c92a9050 RCX: 00007f86c91890f9
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000007
RBP: 00007f86c91e4ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcb857fc2f R14: 00007f86c76da300 R15: 0000000000022000
INFO: task syz-executor.5:12346 blocked for more than 140 seconds.
      Not tainted 4.19.211-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.5  D27344 12346   8135 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2828 [inline]
 __schedule+0x887/0x2040 kernel/sched/core.c:3517
 schedule+0x8d/0x1b0 kernel/sched/core.c:3561
 schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
 __mutex_lock_common kernel/locking/mutex.c:1016 [inline]
 __mutex_lock+0x5f0/0x1190 kernel/locking/mutex.c:1078
 f2fs_balance_fs+0x709/0xd80 fs/f2fs/segment.c:512
 f2fs_setattr+0x5b6/0x12b0 fs/f2fs/file.c:852
 notify_change+0x70b/0xfc0 fs/attr.c:334
 do_truncate+0x134/0x1f0 fs/open.c:63
 handle_truncate fs/namei.c:3009 [inline]
 do_last fs/namei.c:3427 [inline]
 path_openat+0x2308/0x2df0 fs/namei.c:3537
 do_filp_open+0x18c/0x3f0 fs/namei.c:3567
 do_sys_open+0x3b3/0x520 fs/open.c:1085
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f86c91890f9
Code: Bad RIP value.
RSP: 002b:00007f86c3298168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f86c92a91f0 RCX: 00007f86c91890f9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000100
RBP: 00007f86c91e4ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffcb857fc2f R14: 00007f86c3298300 R15: 0000000000022000

Showing all locks held in the system:
1 lock held by ksoftirqd/1/18:
 #0: 0000000078914150 (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
 #0: 0000000078914150 (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
4 locks held by kworker/u4:1/23:
 #0: 00000000eb6e84fb ((wq_completion)"writeback"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
 #1: 00000000c2d1c814 ((work_completion)(&(&wb->dwork)->work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
 #2: 00000000de90c873 (&type->s_umount_key#49){++++}, at: trylock_super+0x1d/0x100 fs/super.c:412
 #3: 0000000071772d10 (&sbi->gc_mutex){+.+.}, at: f2fs_balance_fs+0x709/0xd80 fs/f2fs/segment.c:512
5 locks held by kworker/1:1/34:
 #0: 000000003621274b ((wq_completion)"usb_hub_wq"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
 #1: 000000005f9401af ((work_completion)(&hub->events)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
 #2: 0000000001a4f180 (&dev->mutex){....}, at: device_lock include/linux/device.h:1174 [inline]
 #2: 0000000001a4f180 (&dev->mutex){....}, at: hub_event+0x11e/0x44a0 drivers/usb/core/hub.c:5387
 #3: 000000007b3cc445 (&port_dev->status_lock){+.+.}, at: usb_lock_port drivers/usb/core/hub.c:2983 [inline]
 #3: 000000007b3cc445 (&port_dev->status_lock){+.+.}, at: hub_port_connect drivers/usb/core/hub.c:5069 [inline]
 #3: 000000007b3cc445 (&port_dev->status_lock){+.+.}, at: hub_port_connect_change drivers/usb/core/hub.c:5253 [inline]
 #3: 000000007b3cc445 (&port_dev->status_lock){+.+.}, at: port_event drivers/usb/core/hub.c:5361 [inline]
 #3: 000000007b3cc445 (&port_dev->status_lock){+.+.}, at: hub_event+0x1cb8/0x44a0 drivers/usb/core/hub.c:5441
 #4: 000000006c758e01 (hcd->address0_mutex){+.+.}, at: hub_port_init+0x1b9/0x3120 drivers/usb/core/hub.c:4578
4 locks held by kworker/u4:2/36:
1 lock held by khungtaskd/1563:
 #0: 0000000015b8b4a2 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7818:
 #0: 0000000017b9beb8 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by rs:main Q:Reg/7819:
 #0: 0000000032bbb151 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
 #1: 00000000ddbb506c (sb_writers#3){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline]
 #1: 00000000ddbb506c (sb_writers#3){.+.+}, at: vfs_write+0x463/0x540 fs/read_write.c:548
4 locks held by syz-executor.5/12261:
2 locks held by syz-executor.5/12267:
 #0: 000000009cc97911 (sb_writers#14){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline]
 #0: 000000009cc97911 (sb_writers#14){.+.+}, at: do_sendfile+0x97d/0xc30 fs/read_write.c:1446
 #1: 00000000c7807272 (&sb->s_type->i_mutex_key#21){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 00000000c7807272 (&sb->s_type->i_mutex_key#21){+.+.}, at: f2fs_file_write_iter+0x218/0xbe0 fs/f2fs/file.c:2996
3 locks held by syz-executor.5/12346:
 #0: 000000009cc97911 (sb_writers#14){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 000000009cc97911 (sb_writers#14){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 00000000c7807272 (&sb->s_type->i_mutex_key#21){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 00000000c7807272 (&sb->s_type->i_mutex_key#21){+.+.}, at: do_truncate+0x125/0x1f0 fs/open.c:61
 #2: 0000000071772d10 (&sbi->gc_mutex){+.+.}, at: f2fs_balance_fs+0x709/0xd80 fs/f2fs/segment.c:512

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1563 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1a6/0x1f0 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
 watchdog+0x991/0xe60 kernel/hung_task.c:287
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 36 Comm: kworker/u4:2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/16/2023
Workqueue: bat_events batadv_nc_worker
RIP: 0010:lockdep_hardirqs_on+0x82/0x5c0 kernel/locking/lockdep.c:2849
Code: fc ff df 48 89 fa 48 c1 ea 03 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 38 d0 7c 08 84 d2 0f 85 c1 03 00 00 44 8b 9b 84 08 00 00 <45> 85 db 0f 85 0d 03 00 00 65 48 8b 1c 25 c0 df 01 00 48 8d bb 50
RSP: 0018:ffff8880b513fc08 EFLAGS: 00000046
RAX: 0000000000000007 RBX: ffff8880b512e2c0 RCX: 1ffffffff148be2c
RDX: 0000000000000000 RSI: ffffffff8167a995 RDI: ffff8880b512eb44
RBP: ffffffff813922a9 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: ffff8880b512e2c0
R13: ffffffff87d8da80 R14: 0000000000000045 R15: ffff88809d4a2980
FS:  0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6bdbe9a018 CR3: 00000000a3b99000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 __local_bh_enable_ip+0x159/0x270 kernel/softirq.c:194
 spin_unlock_bh include/linux/spinlock.h:374 [inline]
 batadv_nc_purge_paths+0x22d/0x310 net/batman-adv/network-coding.c:482
 batadv_nc_worker+0x6fa/0xd50 net/batman-adv/network-coding.c:731
 process_one_work+0x864/0x1570 kernel/workqueue.c:2153
 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296
 kthread+0x33f/0x460 kernel/kthread.c:259
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Crashes (5):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/03 18:53 linux-4.19.y 3f8a27f9e27b f8902b57 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in f2fs_file_write_iter
2023/03/03 12:59 linux-4.19.y 3f8a27f9e27b f8902b57 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in f2fs_file_write_iter
2023/02/15 00:20 linux-4.19.y 3f8a27f9e27b e62ba3c1 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in f2fs_file_write_iter
2022/11/30 09:46 linux-4.19.y 3f8a27f9e27b 579a3740 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in f2fs_file_write_iter
2022/11/20 06:59 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in f2fs_file_write_iter
* Struck through repros no longer work on HEAD.