syzbot


INFO: task hung in fuse_launder_page

Status: upstream: reported C repro on 2021/05/03 09:31
Reported-by: syzbot+870bb7df35785306a4b3@syzkaller.appspotmail.com
First crash: 1146d, last: 479d
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in fuse_launder_page C error 59 514d 1140d 0/1 upstream: reported C repro on 2021/05/09 12:49
upstream INFO: task hung in fuse_launder_page fuse C unreliable 1 1048d 1044d 20/27 fixed on 2021/11/10 00:50
Fix bisection attempts (10)
Created Duration User Patch Repo Result
2023/02/28 21:27 32m bisect fix linux-4.14.y job log (0) log
2022/07/28 11:02 26m bisect fix linux-4.14.y job log (0) log
2022/06/28 10:02 19m bisect fix linux-4.14.y job log (0) log
2022/01/29 17:16 25m bisect fix linux-4.14.y job log (0) log
2021/12/30 16:34 29m bisect fix linux-4.14.y job log (0) log
2021/11/30 16:11 21m bisect fix linux-4.14.y job log (0) log
2021/10/20 05:33 21m bisect fix linux-4.14.y job log (0) log
2021/09/20 05:09 24m bisect fix linux-4.14.y job log (0) log
2021/08/21 04:45 23m bisect fix linux-4.14.y job log (0) log
2021/07/22 04:20 25m bisect fix linux-4.14.y job log (0) log

Sample crash report:
INFO: task syz-executor374:7984 blocked for more than 140 seconds.
      Not tainted 4.14.304-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor374 D28448  7984   7982 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2811 [inline]
 __schedule+0x88b/0x1de0 kernel/sched/core.c:3387
 schedule+0x8d/0x1b0 kernel/sched/core.c:3431
 fuse_wait_on_page_writeback fs/fuse/file.c:385 [inline]
 fuse_wait_on_page_writeback.isra.0+0xdc/0x120 fs/fuse/file.c:381
 fuse_launder_page fs/fuse/file.c:2042 [inline]
 fuse_launder_page+0xa2/0xd0 fs/fuse/file.c:2035
 do_launder_page mm/truncate.c:609 [inline]
 invalidate_inode_pages2_range+0x547/0xc00 mm/truncate.c:685
 fuse_finish_open+0x262/0x500 fs/fuse/file.c:181
 fuse_open_common+0x234/0x290 fs/fuse/file.c:224
 do_dentry_open+0x44b/0xec0 fs/open.c:777
 vfs_open+0x105/0x220 fs/open.c:888
 do_last fs/namei.c:3428 [inline]
 path_openat+0x628/0x2970 fs/namei.c:3571
 do_filp_open+0x179/0x3c0 fs/namei.c:3605
 do_sys_open+0x296/0x410 fs/open.c:1081
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f6be7bfa4c9
RSP: 002b:00007f6be7bab2f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f6be7c8b4c0 RCX: 00007f6be7bfa4c9
RDX: 0000000000000000 RSI: 0000000000003f00 RDI: 0000000020000080
RBP: 00007f6be7c58164 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0030656c69662f2e
R13: 00007f6be7c54158 R14: 00007f6be7c56160 R15: 00007f6be7c8b4c8

Showing all locks held in the system:
1 lock held by khungtaskd/1534:
 #0:  (tasklist_lock){.+.+}, at: [<ffffffff8702d8de>] debug_show_all_locks+0x7c/0x21a kernel/locking/lockdep.c:4548
1 lock held by systemd-journal/4625:
 #0:  (&rq->lock){-.-.}, at: [<ffffffff813dbfa4>] idle_balance kernel/sched/fair.c:8471 [inline]
 #0:  (&rq->lock){-.-.}, at: [<ffffffff813dbfa4>] pick_next_task_fair+0x554/0x1450 kernel/sched/fair.c:6379
2 locks held by syz-executor374/7984:
 #0:  (sb_writers#10){.+.+}, at: [<ffffffff818e1d0a>] sb_start_write include/linux/fs.h:1551 [inline]
 #0:  (sb_writers#10){.+.+}, at: [<ffffffff818e1d0a>] mnt_want_write+0x3a/0xb0 fs/namespace.c:386
 #1:  (&sb->s_type->i_mutex_key#17){+.+.}, at: [<ffffffff822f7bd4>] inode_lock include/linux/fs.h:719 [inline]
 #1:  (&sb->s_type->i_mutex_key#17){+.+.}, at: [<ffffffff822f7bd4>] fuse_open_common+0x1a4/0x290 fs/fuse/file.c:217

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

NMI backtrace for cpu 1
CPU: 1 PID: 1534 Comm: khungtaskd Not tainted 4.14.304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 nmi_cpu_backtrace.cold+0x57/0x93 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x13a/0x180 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:140 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:195 [inline]
 watchdog+0x5b9/0xb40 kernel/hung_task.c:274
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4625 Comm: systemd-journal Not tainted 4.14.304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
task: ffff8880a11f2180 task.stack: ffff8880a11f8000
RIP: 0010:lock_unpin_lock+0x0/0x410 kernel/locking/lockdep.c:4082
RSP: 0018:ffff8880a11ffaa8 EFLAGS: 00000046
RAX: ffff8880a11ffc10 RBX: 000000010000da89 RCX: 1ffffffff0f13638
RDX: dffffc0000000000 RSI: 000000000000e3f4 RDI: ffff8880ba434418
RBP: ffff8880ba434400 R08: ffff8880ba434510 R09: ffff8880a11f2358
R10: ffff8880a11f2388 R11: 0000000000000000 R12: 0000000000000000
R13: 000000c7dabaee74 R14: ffff8880a11f8000 R15: dffffc0000000000
FS:  00007ffb4071c8c0(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffb3daeb010 CR3: 00000000a129f000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 rq_unpin_lock kernel/sched/sched.h:943 [inline]
 idle_balance kernel/sched/fair.c:8417 [inline]
 pick_next_task_fair+0x1d5/0x1450 kernel/sched/fair.c:6379
 pick_next_task kernel/sched/core.c:3235 [inline]
 __schedule+0x502/0x1de0 kernel/sched/core.c:3360
 schedule+0x8d/0x1b0 kernel/sched/core.c:3431
 schedule_hrtimeout_range_clock+0x2d0/0x320 kernel/time/hrtimer.c:1707
 ep_poll+0x85e/0xa50 fs/eventpoll.c:1827
 SYSC_epoll_wait fs/eventpoll.c:2195 [inline]
 SyS_epoll_wait+0x150/0x1a0 fs/eventpoll.c:2160
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7ffb3f9e52e3
RSP: 002b:00007ffcf0635618 EFLAGS: 00000246 ORIG_RAX: 00000000000000e8
RAX: ffffffffffffffda RBX: 0000563c734211e0 RCX: 00007ffb3f9e52e3
RDX: 0000000000000013 RSI: 00007ffcf0635620 RDI: 0000000000000008
RBP: 00007ffcf0635810 R08: 00007ffcf0658000 R09: 000000dd6a6b62b6
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffcf0635620
R13: 0000000000000001 R14: ffffffffffffffff R15: 0005f34145ae10e9
Code: 7c ff ff ff e8 c2 c0 3d 00 e9 56 ff ff ff e8 a8 c1 3d 00 e9 d0 fe ff ff e8 7e c2 3d 00 e9 3e fe ff ff 66 0f 1f 84 00 00 00 00 00 <41> 57 41 56 41 55 41 54 49 89 fc 55 53 48 83 ec 58 48 c7 44 24 

Crashes (45):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/27 16:24 linux-4.14.y 3949d1610004 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/26 14:55 linux-4.14.y 3949d1610004 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/15 23:28 linux-4.14.y c4215ee4771b a63719e7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/13 01:33 linux-4.14.y c4215ee4771b 96166539 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/07 07:55 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/07 00:28 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2023/01/06 12:21 linux-4.14.y c4215ee4771b 1dac8c7a .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/12/12 11:48 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/12/12 02:18 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/12/11 19:14 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/12/11 12:36 linux-4.14.y 65afe34ac33d 67be1ae7 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/12/05 10:54 linux-4.14.y 179ef7fe8677 e080de16 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/26 23:34 linux-4.14.y 179ef7fe8677 f4470a7b .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/20 04:39 linux-4.14.y e911713e40ca 5bb70014 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/19 22:07 linux-4.14.y e911713e40ca 5bb70014 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/07 08:28 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/07 01:33 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/06 18:34 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/06 11:07 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/06 04:22 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/05 21:48 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/05 08:05 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/11/04 14:19 linux-4.14.y a901bb6c7db7 6d752409 .config console log report syz C [disk image] [vmlinux] [kernel image] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/10/19 16:14 linux-4.14.y 9d5c0b3a8e1a b31320fc .config console log report syz C [disk image] [vmlinux] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/10/06 12:26 linux-4.14.y 9d5c0b3a8e1a 2c6543ad .config console log report syz C [disk image] [vmlinux] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/10/01 10:37 linux-4.14.y 9d5c0b3a8e1a feb56351 .config console log report syz C [disk image] [vmlinux] ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/08/28 03:00 linux-4.14.y e548869f356f 07177916 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/05/29 09:48 linux-4.14.y 501eec4f9e13 a46af346 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/05/29 01:51 linux-4.14.y 501eec4f9e13 a46af346 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/05/10 22:17 linux-4.14.y e3a56aaade89 8b277b8e .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/05/01 03:04 linux-4.14.y e3a56aaade89 2df221f6 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/04/19 05:27 linux-4.14.y 74766a973637 8bcc32a6 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/04/14 22:53 linux-4.14.y 74766a973637 b17b2923 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/04/10 23:42 linux-4.14.y 74766a973637 e22c3da3 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/27 09:27 linux-4.14.y 004bfaafc45c 89bc8608 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/27 02:23 linux-4.14.y 004bfaafc45c 89bc8608 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/20 08:36 linux-4.14.y eb045674aab3 e2d91b1d .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/20 02:01 linux-4.14.y eb045674aab3 e2d91b1d .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/19 06:09 linux-4.14.y eb045674aab3 e2d91b1d .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/18 18:15 linux-4.14.y eb045674aab3 e2d91b1d .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/03/15 18:40 linux-4.14.y af48f51cb593 9e8eaa75 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2022/02/15 14:06 linux-4.14.y 8034e99d1a01 8b9ca619 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2021/10/31 15:57 linux-4.14.y cd5296934610 098b5d53 .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2021/06/22 04:20 linux-4.14.y cfb41ef9deb1 aba2b2fb .config console log report syz C ci2-linux-4-14 INFO: task hung in fuse_launder_page
2021/05/03 09:30 linux-4.14.y 7d7d1c0ab3eb 77e2b668 .config console log report info ci2-linux-4-14 INFO: task hung in fuse_launder_page
* Struck through repros no longer work on HEAD.