INFO: task hung in fuse_direct_IO

[syzbot]

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=11c68ba6700000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=a5f87cabbba8ea69db77
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+a5f87c...@syzkaller.appspotmail.com

ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
INFO: task syz-executor.1:5083 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.1 D28408 5083 14755 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_timeout+0x92d/0xfe0 kernel/time/timer.c:1794
do_wait_for_common kernel/sched/completion.c:83 [inline]
__wait_for_common kernel/sched/completion.c:104 [inline]
wait_for_common+0x29c/0x470 kernel/sched/completion.c:115
fuse_direct_IO+0x89a/0xe20 fs/fuse/file.c:2942
generic_file_direct_write+0x208/0x4a0 mm/filemap.c:3073
fuse_file_write_iter+0x55d/0x900 fs/fuse/file.c:1216
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:0x7fbb55214059
Code: Bad RIP value.
RSP: 002b:00007fbb53b68168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fbb55327030 RCX: 00007fbb55214059
RDX: 0000000000000018 RSI: 0000000020000340 RDI: 0000000000000005
RBP: 00007fbb5526e08d R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc6d4ce8ef R14: 00007fbb53b68300 R15: 0000000000022000

Showing all locks held in the system:
1 lock held by khungtaskd/1570:
#0: 00000000b1eb097c (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7800:
#0: 0000000015d31670 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
3 locks held by syz-executor.1/5083:
#0: 00000000e92a51d0 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
#1: 00000000d65d69db (sb_writers#19){.+.+}, at: file_start_write include/linux/fs.h:2779 [inline]
#1: 00000000d65d69db (sb_writers#19){.+.+}, at: vfs_write+0x463/0x540 fs/read_write.c:548
#2: 000000003d85f46b (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
#2: 000000003d85f46b (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_file_write_iter+0x174/0x900 fs/fuse/file.c:1197

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

NMI backtrace for cpu 1
CPU: 1 PID: 1570 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: 9507 Comm: kworker/u4:8 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: phy28 ieee80211_iface_work
RIP: 0010:write_comp_data+0x23/0x70 kernel/kcov.c:122
Code: 1f 84 00 00 00 00 00 49 89 f1 49 89 fa 65 48 8b 34 25 c0 df 01 00 65 8b 05 7a 59 9f 7e a9 00 01 1f 00 75 4f 8b 86 60 13 00 00 <83> f8 03 75 44 48 8b 86 68 13 00 00 8b b6 64 13 00 00 48 8b 38 48
RSP: 0018:ffff88804f4efca8 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000003 RCX: ffffffff879b734b
RDX: 0000000000000001 RSI: ffff8880af1c03c0 RDI: 0000000000000005
RBP: ffffffff89679220 R08: 0000000000000000 R09: 0000000000000007
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000000005
R13: 0000000000000003 R14: ffff88804becb780 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880ba000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff817547000 CR3: 00000000a9827000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__sanitizer_cov_trace_switch+0x4b/0x80 kernel/kcov.c:224
ieee80211_iface_work+0x24b/0x8a0 net/mac80211/iface.c:1336
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
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 84 00 test %al,(%rax)
2: 00 00 add %al,(%rax)
4: 00 00 add %al,(%rax)
6: 49 89 f1 mov %rsi,%r9
9: 49 89 fa mov %rdi,%r10
c: 65 48 8b 34 25 c0 df mov %gs:0x1dfc0,%rsi
13: 01 00
15: 65 8b 05 7a 59 9f 7e mov %gs:0x7e9f597a(%rip),%eax # 0x7e9f5996
1c: a9 00 01 1f 00 test $0x1f0100,%eax
21: 75 4f jne 0x72
23: 8b 86 60 13 00 00 mov 0x1360(%rsi),%eax
* 29: 83 f8 03 cmp $0x3,%eax <-- trapping instruction
2c: 75 44 jne 0x72
2e: 48 8b 86 68 13 00 00 mov 0x1368(%rsi),%rax
35: 8b b6 64 13 00 00 mov 0x1364(%rsi),%esi
3b: 48 8b 38 mov (%rax),%rdi
3e: 48 rex.W


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.