syzbot


INFO: task hung in fuse_flush (3)

Status: upstream: reported on 2022/01/27 11:57
Reported-by: syzbot+c730d0c38583d5d6c3af@syzkaller.appspotmail.com
First crash: 813d, last: 451d
Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in fuse_flush 1 1128d 1128d 0/1 auto-closed as invalid on 2021/07/16 16:14
upstream INFO: task hung in fuse_flush (2) fuse 2 452d 461d 0/26 auto-obsoleted due to no activity on 2023/04/24 00:25
upstream INFO: task hung in fuse_flush fuse 2 897d 985d 0/26 auto-closed as invalid on 2022/02/03 03:15
linux-4.19 INFO: task hung in fuse_flush (2) 1 937d 937d 0/1 auto-closed as invalid on 2022/01/24 04:40
linux-4.14 INFO: task hung in fuse_flush C inconclusive 19 493d 814d 0/1 upstream: reported C repro on 2022/01/26 21:17
upstream INFO: task hung in fuse_flush (3) fuse 1 205d 205d 0/26 auto-obsoleted due to no activity on 2023/12/26 21:09

Sample crash report:
ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
Bluetooth: hci7: command 0x041b tx timeout
Bluetooth: hci7: command 0x040f tx timeout
Bluetooth: hci7: command 0x0419 tx timeout
INFO: task syz-executor.5:13622 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 13622   8134 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:0x7ff6e273af7b
Code: Bad RIP value.
RSP: 002b:00007ffe890a57a0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007ff6e273af7b
RDX: 0000001b2ec20000 RSI: 0000001b2ec2667c RDI: 0000000000000004
RBP: 00007ff6e28aa980 R08: 0000000000000000 R09: 000000003253460c
R10: 0019671678d57847 R11: 0000000000000293 R12: 000000000003fed9
R13: 00007ffe890a58a0 R14: 00007ff6e28a9120 R15: 0000000000000032
INFO: task syz-executor.5:13631 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  D27592 13631   8134 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:0x7ff6e27890c9
Code: Bad RIP value.
RSP: 002b:00007ff6e0cfb168 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007ff6e28a8f80 RCX: 00007ff6e27890c9
RDX: 0000000000000000 RSI: 0000000000003f00 RDI: 0000000020000080
RBP: 00007ff6e27e4ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe890a573f R14: 00007ff6e0cfb300 R15: 0000000000022000
INFO: task syz-executor.5:13636 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  D29464 13636   8134 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_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
 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:0x7ff6e27890c9
Code: Bad RIP value.
RSP: 002b:00007ff6e0cda168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007ff6e28a9050 RCX: 00007ff6e27890c9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200001c0
RBP: 00007ff6e27e4ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe890a573f R14: 00007ff6e0cda300 R15: 0000000000022000

Showing all locks held in the system:
1 lock held by khungtaskd/1572:
 #0: 000000007e0bb90f (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4441
1 lock held by in:imklog/7823:
1 lock held by syz-executor.5/13622:
 #0: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #0: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_flush+0x1fd/0x5b0 fs/fuse/file.c:421
2 locks held by syz-executor.5/13631:
 #0: 000000006b0639cb (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 000000006b0639cb (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
2 locks held by syz-executor.5/13636:
 #0: 000000006b0639cb (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 000000006b0639cb (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 000000008408f91d (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
1 lock held by syz-executor.5/14016:
 #0: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #0: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_flush+0x1fd/0x5b0 fs/fuse/file.c:421
2 locks held by syz-executor.5/14017:
 #0: 00000000ce26dbfc (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 00000000ce26dbfc (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
2 locks held by syz-executor.5/14020:
 #0: 00000000ce26dbfc (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 00000000ce26dbfc (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 000000005ed38063 (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
1 lock held by syz-executor.5/14326:
 #0: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #0: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_flush+0x1fd/0x5b0 fs/fuse/file.c:421
2 locks held by syz-executor.5/14327:
 #0: 0000000086adf55c (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 0000000086adf55c (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215
2 locks held by syz-executor.5/14330:
 #0: 0000000086adf55c (sb_writers#17){.+.+}, at: sb_start_write include/linux/fs.h:1579 [inline]
 #0: 0000000086adf55c (sb_writers#17){.+.+}, at: mnt_want_write+0x3a/0xb0 fs/namespace.c:360
 #1: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: inode_lock include/linux/fs.h:748 [inline]
 #1: 00000000f0022a9e (&sb->s_type->i_mutex_key#26){+.+.}, at: fuse_open_common+0x1bc/0x2c0 fs/fuse/file.c:215

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

NMI backtrace for cpu 0
CPU: 0 PID: 1572 Comm: khungtaskd Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/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: 7824 Comm: rs:main Q:Reg Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
RIP: 0010:memset_erms+0x9/0x10 arch/x86/lib/memset_64.S:66
Code: c1 e9 03 40 0f b6 f6 48 b8 01 01 01 01 01 01 01 01 48 0f af c6 f3 48 ab 89 d1 f3 aa 4c 89 c8 c3 90 49 89 f9 40 88 f0 48 89 d1 <f3> aa 4c 89 c8 c3 90 49 89 fa 40 0f b6 ce 48 b8 01 01 01 01 01 01
RSP: 0018:ffff8880a4c6f810 EFLAGS: 00010246
RAX: ffffed1008a7dc00 RBX: 0000000000001000 RCX: 0000000000000940
RDX: 0000000000000ccc RSI: 0000000000000000 RDI: ffff8880453ed6c0
RBP: 0000000000000000 R08: 0000000000000001 R09: ffff8880453ed334
R10: ffff8880453edfff R11: 0000000000000000 R12: 0000000000000334
R13: 0000000000001000 R14: 0000000000000000 R15: 0000000000000000
FS:  00007f5f70d07700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff205332000 CR3: 0000000092c66000 CR4: 00000000003406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 memset include/linux/string.h:362 [inline]
 zero_user_segments include/linux/highmem.h:203 [inline]
 __block_write_begin_int+0x11f2/0x17b0 fs/buffer.c:1994
 ext4_da_write_begin+0x4e1/0x10e0 fs/ext4/inode.c:3109
 generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
 __generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
 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:0x7f5f7374b1cd
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:00007f5f70d06590 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f5f68007090 RCX: 00007f5f7374b1cd
RDX: 0000000000000456 RSI: 00007f5f68007090 RDI: 0000000000000006
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000293 R12: 00007f5f68006e10
R13: 00007f5f70d065b0 R14: 0000556952f90360 R15: 0000000000000456

Crashes (109):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/24 12:04 linux-4.19.y 3f8a27f9e27b 9dfcf09c .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2023/01/21 12:38 linux-4.19.y 3f8a27f9e27b cc0f9968 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2023/01/16 16:34 linux-4.19.y 3f8a27f9e27b a63719e7 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2023/01/05 21:02 linux-4.19.y 3f8a27f9e27b 1dac8c7a .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2023/01/04 15:13 linux-4.19.y 3f8a27f9e27b 1dac8c7a .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/29 05:24 linux-4.19.y 3f8a27f9e27b 44712fbc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/28 10:50 linux-4.19.y 3f8a27f9e27b 44712fbc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/27 07:52 linux-4.19.y 3f8a27f9e27b 9da18ae8 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/27 02:43 linux-4.19.y 3f8a27f9e27b 9da18ae8 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/25 23:53 linux-4.19.y 3f8a27f9e27b 9da18ae8 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/25 13:52 linux-4.19.y 3f8a27f9e27b 9da18ae8 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/21 16:46 linux-4.19.y 3f8a27f9e27b 4067838e .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/11 12:20 linux-4.19.y 3f8a27f9e27b 67be1ae7 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/11 09:48 linux-4.19.y 3f8a27f9e27b 67be1ae7 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/11 08:46 linux-4.19.y 3f8a27f9e27b 67be1ae7 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/05 12:11 linux-4.19.y 3f8a27f9e27b e080de16 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/02 14:40 linux-4.19.y 3f8a27f9e27b e080de16 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/12/02 08:20 linux-4.19.y 3f8a27f9e27b e080de16 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/28 08:26 linux-4.19.y 3f8a27f9e27b f4470a7b .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/27 23:17 linux-4.19.y 3f8a27f9e27b f4470a7b .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/26 06:58 linux-4.19.y 3f8a27f9e27b f4470a7b .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/25 23:53 linux-4.19.y 3f8a27f9e27b f4470a7b .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/25 18:14 linux-4.19.y 3f8a27f9e27b 74a66371 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/21 08:26 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/21 00:57 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/18 05:34 linux-4.19.y 3f8a27f9e27b 5bb70014 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/16 05:35 linux-4.19.y 3f8a27f9e27b 3a127a31 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/15 01:38 linux-4.19.y 3f8a27f9e27b 97de9cfc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/05 21:24 linux-4.19.y 3f8a27f9e27b 6d752409 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/04 05:50 linux-4.19.y 3f8a27f9e27b 6d752409 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/03 09:27 linux-4.19.y 3f8a27f9e27b 7a2ebf95 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/11/02 00:45 linux-4.19.y 3f8a27f9e27b 08977f5d .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/27 14:56 linux-4.19.y 3f8a27f9e27b 5c716ff6 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/26 21:10 linux-4.19.y 3f8a27f9e27b 86777b7f .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/25 00:53 linux-4.19.y 3f8a27f9e27b faae2fda .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/24 22:23 linux-4.19.y 3f8a27f9e27b faae2fda .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/24 21:18 linux-4.19.y 3f8a27f9e27b faae2fda .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/24 20:04 linux-4.19.y 3f8a27f9e27b faae2fda .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/20 15:04 linux-4.19.y 3f8a27f9e27b b31320fc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/19 09:14 linux-4.19.y 3f8a27f9e27b b31320fc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/19 05:46 linux-4.19.y 3f8a27f9e27b b31320fc .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/18 00:16 linux-4.19.y 3f8a27f9e27b 94744d21 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/10/06 02:55 linux-4.19.y 3f8a27f9e27b 2c6543ad .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/30 15:12 linux-4.19.y 3f8a27f9e27b 45fd7169 .config console log report info ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/28 23:15 linux-4.19.y 3f8a27f9e27b a41a2080 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/28 23:14 linux-4.19.y 3f8a27f9e27b a41a2080 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/28 22:49 linux-4.19.y 3f8a27f9e27b a41a2080 .config console log report info [disk image] [vmlinux] ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/25 01:54 linux-4.19.y 3f8a27f9e27b 0042f2b4 .config console log report info ci2-linux-4-19 INFO: task hung in fuse_flush
2022/09/25 01:44 linux-4.19.y 3f8a27f9e27b 0042f2b4 .config console log report info ci2-linux-4-19 INFO: task hung in fuse_flush
2022/01/27 11:57 linux-4.19.y 3f8a27f9e27b 2cbffd88 .config console log report info ci2-linux-4-19 INFO: task hung in fuse_flush
* Struck through repros no longer work on HEAD.