INFO: task hung in f2fs_file_write_iter

6 views
Skip to first unread message

syzbot

unread,
Nov 20, 2022, 2:00:38 AM11/20/22
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=115f26dd880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=656e8503e4a4f31ebf36
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+656e85...@syzkaller.appspotmail.com

F2FS-fs (loop3): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 24
F2FS-fs (loop3): sanity_check_inode: inode (ino=8) has corrupted i_extra_isize: 36, max: 24
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task syz-executor.3:13716 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.3 D22592 13716 8184 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:0x7fe6b3bf3639
Code: Bad RIP value.
RSP: 002b:00007fe6b2166168 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fe6b3d13f80 RCX: 00007fe6b3bf3639
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000004
RBP: 00007fe6b3c4eae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc46b54f1f R14: 00007fe6b2166300 R15: 0000000000022000

Showing all locks held in the system:
2 locks held by kworker/u4:0/7:
#0: 00000000653c37ef (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
#0: 00000000653c37ef (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
#1: 00000000d827d467 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 00000000d827d467 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
4 locks held by kworker/u4:1/23:
#0: 00000000b6be0a52 ((wq_completion)"writeback"){+.+.}, at: process_one_work+0x767/0x1570 kernel/workqueue.c:2124
#1: 0000000008996504 ((work_completion)(&(&wb->dwork)->work)){+.+.}, at: process_one_work+0x79c/0x1570 kernel/workqueue.c:2128
#2: 0000000022be0adf (&type->s_umount_key#81){++++}, at: trylock_super+0x1d/0x100 fs/super.c:412
#3: 00000000c8c33c75 (&sbi->gc_mutex){+.+.}, at: f2fs_balance_fs+0x709/0xd80 fs/f2fs/segment.c:512
1 lock held by khungtaskd/1570:
#0: 00000000d827d467 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7821:
#0: 000000009051abba (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by kworker/u4:6/8835:
#0: 00000000653c37ef (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
#0: 00000000653c37ef (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
#1: 00000000d827d467 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 00000000d827d467 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
#2: 00000000d827d467 (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#2: 00000000d827d467 (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
2 locks held by syz-executor.3/13716:
#0: 00000000cfa572d6 (sb_writers#22){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline]
#0: 00000000cfa572d6 (sb_writers#22){.+.+}, at: do_sendfile+0x97d/0xc30 fs/read_write.c:1446
#1: 00000000291f7ac2 (&sb->s_type->i_mutex_key#28){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#1: 00000000291f7ac2 (&sb->s_type->i_mutex_key#28){+.+.}, at: f2fs_file_write_iter+0x218/0xbe0 fs/f2fs/file.c:2996
3 locks held by syz-executor.3/13725:
2 locks held by syz-executor.3/14027:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14029:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14030:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14031:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14032:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14520:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14531:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14539:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14541:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457
2 locks held by syz-executor.3/14551:
#0: 0000000022be0adf (&type->s_umount_key#81){++++}, at: iterate_supers+0xdb/0x290 fs/super.c:631
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:338 [inline]
#1: 0000000005931323 (&bdi->wb_switch_rwsem){+.+.}, at: sync_inodes_sb+0x180/0x9a0 fs/fs-writeback.c:2457

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

NMI backtrace for cpu 0
CPU: 0 PID: 1570 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
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: 39 Comm: kworker/u4:2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Workqueue: bat_events batadv_nc_worker
RIP: 0010:__lock_acquire+0x4f1/0x3ff0 kernel/locking/lockdep.c:3371
Code: 00 25 ff 1f 00 00 c1 e5 14 41 09 ec 41 09 c4 48 b8 00 00 00 00 00 fc ff df 45 89 62 20 0f b6 14 02 48 89 f8 83 e0 07 83 c0 03 <38> d0 7c 08 84 d2 0f 85 0f 26 00 00 8b 84 24 e8 01 00 00 45 85 ff
RSP: 0018:ffff8880b517f9e8 EFLAGS: 00000002
RAX: 0000000000000007 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 1ffff11016a2e18a RDI: ffff8880b5170c7c
RBP: 0000000000000000 R08: 0000000000000618 R09: 0000000000000002
R10: ffff8880b5170c58 R11: 0000000000000000 R12: 0000000000040618
R13: ffff8880b5170380 R14: ffff8880b5170c70 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f15f552d000 CR3: 0000000095c58000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:168
spin_lock_bh include/linux/spinlock.h:334 [inline]
batadv_nc_purge_paths+0xdc/0x310 net/batman-adv/network-coding.c:453
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


---
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.
Reply all
Reply to author
Forward
0 new messages