INFO: task hung in fuse_flush (3)

6 views
Skip to first unread message

syzbot

unread,
Jan 27, 2022, 6:57:23 AM1/27/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=171928e0700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=c730d0c38583d5d6c3af
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

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

wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
wlan1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task syz-executor.5:20425 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 D28648 20425 8142 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]
fuse_flush+0x1fd/0x5b0 fs/fuse/file.c:421
filp_close+0xb4/0x160 fs/open.c:1162
__close_fd+0x133/0x200 fs/file.c:636
__do_sys_close fs/open.c:1181 [inline]
__se_sys_close fs/open.c:1179 [inline]
__x64_sys_close+0x69/0x100 fs/open.c:1179
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fd3d6293c9b
Code: Bad RIP value.
RSP: 002b:00007ffea1d596e0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fd3d6293c9b
RDX: 0000001b30420000 RSI: 0000001b30426748 RDI: 0000000000000004
RBP: 00007fd3d63f5960 R08: 0000000000000000 R09: 000000003253460c
R10: 000d2636fd984dfb R11: 0000000000000293 R12: 00000000000dec38
R13: 00007ffea1d597e0 R14: 00007ffea1d59800 R15: 0000000000000032
INFO: task syz-executor.5:20429 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 D26888 20429 8142 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
fuse_wait_on_page_writeback fs/fuse/file.c:383 [inline]
fuse_wait_on_page_writeback.isra.0+0x11b/0x170 fs/fuse/file.c:379
fuse_launder_page fs/fuse/file.c:2033 [inline]
fuse_launder_page+0xb6/0xe0 fs/fuse/file.c:2026
do_launder_page mm/truncate.c:655 [inline]
invalidate_inode_pages2_range+0x795/0x1110 mm/truncate.c:725
fuse_finish_open+0x2e2/0x590 fs/fuse/file.c:182
fuse_open_common+0x254/0x2c0 fs/fuse/file.c:222
do_dentry_open+0x4aa/0x1160 fs/open.c:796
do_last fs/namei.c:3421 [inline]
path_openat+0x793/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:0x7fd3d62e1059
Code: Bad RIP value.
RSP: 002b:00007fd3d4c56168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007fd3d63f3f60 RCX: 00007fd3d62e1059
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000000
RBP: 00007fd3d633b08d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffea1d5967f R14: 00007fd3d4c56300 R15: 0000000000022000
INFO: task syz-executor.5:20439 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 D29016 20439 8142 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]
fuse_file_fallocate+0x463/0x840 fs/fuse/file.c:2983
vfs_fallocate+0x487/0x9a0 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+0xcf/0x140 fs/open.c:337
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fd3d62e1059
Code: Bad RIP value.
RSP: 002b:00007fd3d4c35168 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fd3d63f4030 RCX: 00007fd3d62e1059
RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000004
RBP: 00007fd3d633b08d R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000003ff R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffea1d5967f R14: 00007fd3d4c35300 R15: 0000000000022000

Showing all locks held in the system:
1 lock held by khungtaskd/1571:
#0: 0000000005f4e66e (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7836:
2 locks held by kworker/u4:10/22204:
#0: 0000000048f3416b (&rq->lock){-.-.}, at: rq_lock kernel/sched/sched.h:1826 [inline]
#0: 0000000048f3416b (&rq->lock){-.-.}, at: __schedule+0x1f9/0x2040 kernel/sched/core.c:3455
#1: 0000000005f4e66e (rcu_read_lock){....}, at: trace_sched_stat_runtime include/trace/events/sched.h:428 [inline]
#1: 0000000005f4e66e (rcu_read_lock){....}, at: update_curr+0x2c3/0x870 kernel/sched/fair.c:857
3 locks held by kworker/u4:12/22377:
#0: 0000000048f3416b (&rq->lock){-.-.}, at: idle_balance kernel/sched/fair.c:9702 [inline]
#0: 0000000048f3416b (&rq->lock){-.-.}, at: pick_next_task_fair+0x556/0x1570 kernel/sched/fair.c:6841
#1: 0000000005f4e66e (rcu_read_lock){....}, at: cpu_of kernel/sched/sched.h:923 [inline]
#1: 0000000005f4e66e (rcu_read_lock){....}, at: __update_idle_core+0x39/0x3e0 kernel/sched/fair.c:6057
#2: 0000000033313463 (&base->lock){-.-.}, at: lock_timer_base+0x55/0x1b0 kernel/time/timer.c:950
2 locks held by agetty/11285:
#0: 00000000d21067ef (&tty->ldisc_sem){++++}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:272
#1: 0000000059a8b9f0 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x217/0x1950 drivers/tty/n_tty.c:2154
1 lock held by syz-executor.5/20425:
#0: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#0: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: fuse_flush+0x1fd/0x5b0 fs/fuse/file.c:421
2 locks held by syz-executor.5/20429:
#0: 000000002eb119fd (sb_writers#27){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
#0: 000000002eb119fd (sb_writers#27){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
#1: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#1: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
2 locks held by syz-executor.5/20439:
#0: 000000002eb119fd (sb_writers#27){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline]
#0: 000000002eb119fd (sb_writers#27){.+.+}, at: vfs_fallocate+0x7c0/0x9a0 fs/open.c:307
#1: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#1: 00000000671c05ca (&sb->s_type->i_mutex_key#34){+.+.}, at: fuse_file_fallocate+0x463/0x840 fs/fuse/file.c:2983

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

NMI backtrace for cpu 1
CPU: 1 PID: 1571 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 7840 Comm: rs:main Q:Reg Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:inode_peek_iversion include/linux/iversion.h:264 [inline]
RIP: 0010:ext4_inode_peek_iversion fs/ext4/inode.c:4841 [inline]
RIP: 0010:ext4_do_update_inode fs/ext4/inode.c:5355 [inline]
RIP: 0010:ext4_mark_iloc_dirty+0x154f/0x2b30 fs/ext4/inode.c:5919
Code: 4c 89 e7 e8 03 6d b8 ff 4c 89 e2 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 8b 11 00 00 49 8b 9f d8 01 00 00 <48> d1 eb e8 69 a3 82 ff 48 8d 7d 24 41 89 dc 48 b8 00 00 00 00 00
RSP: 0018:ffff88809670f800 EFLAGS: 00000246
RAX: dffffc0000000000 RBX: 0000000000000002 RCX: ffffffff81dfe1dd
RDX: 1ffff11011c0b531 RSI: 0000000000000008 RDI: ffff88808e05a988
RBP: ffff888095d27900 R08: 0000000000000000 R09: ffffed1011c0b531
R10: ffff88808e05a98f R11: 0000000000000000 R12: ffff88808e05a988
R13: 000000000000000f R14: dffffc0000000000 R15: ffff88808e05a7b0
FS: 00007fdaed9b7700(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5c70b3d000 CR3: 00000000a23ff000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_mark_inode_dirty+0x21a/0x870 fs/ext4/inode.c:6113
ext4_dirty_inode+0x88/0xb0 fs/ext4/inode.c:6144
__mark_inode_dirty+0x16b/0x1140 fs/fs-writeback.c:2164
generic_update_time+0x21c/0x370 fs/inode.c:1659
update_time fs/inode.c:1675 [inline]
file_update_time+0x316/0x500 fs/inode.c:1890
__generic_file_write_iter+0x1bc/0x610 mm/filemap.c:3245
ext4_file_write_iter+0x2fe/0xf20 fs/ext4/file.c:272
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fdaf03fb1cd
Code: c2 20 00 00 75 10 b8 01 00 00 00 0f 05 48 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 ae fc ff ff 48 89 04 24 b8 01 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 f7 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007fdaed9b6590 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fdae4024090 RCX: 00007fdaf03fb1cd
RDX: 0000000000000403 RSI: 00007fdae4024090 RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 00007fdae4023e10
R13: 00007fdaed9b65b0 R14: 000055d3a36e8360 R15: 0000000000000403
----------------
Code disassembly (best guess):
0: 4c 89 e7 mov %r12,%rdi
3: e8 03 6d b8 ff callq 0xffb86d0b
8: 4c 89 e2 mov %r12,%rdx
b: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
12: fc ff df
15: 48 c1 ea 03 shr $0x3,%rdx
19: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
1d: 0f 85 8b 11 00 00 jne 0x11ae
23: 49 8b 9f d8 01 00 00 mov 0x1d8(%r15),%rbx
* 2a: 48 d1 eb shr %rbx <-- trapping instruction
2d: e8 69 a3 82 ff callq 0xff82a39b
32: 48 8d 7d 24 lea 0x24(%rbp),%rdi
36: 41 89 dc mov %ebx,%r12d
39: 48 rex.W
3a: b8 00 00 00 00 mov $0x0,%eax


---
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