syzbot


INFO: task hung in pagecache_get_page

Status: closed as dup on 2017/12/12 16:52
Reported-by: syzbot+d32d1ce36ec857115b638b70c3e23772f10d7462@syzkaller.appspotmail.com
First crash: 1710d, last: 1387d
Duplicate of (1):
Title Repro Cause bisect Fix bisect Count Last Reported
INFO: task hung in lo_ioctl 47 1584d 1701d
similar bugs (4):
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-49 INFO: task hung in pagecache_get_page 89 1510d 1642d 0/3 auto-closed as invalid on 2019/02/22 12:49
android-44 INFO: task hung in pagecache_get_page 9 1564d 1618d 0/2 auto-closed as invalid on 2019/02/22 15:22
upstream INFO: task hung in pagecache_get_page (2) 1 717d 717d 0/23 auto-closed as invalid on 2020/11/17 18:29
android-49 INFO: task hung in pagecache_get_page (2) 2 1191d 1199d 0/3 auto-closed as invalid on 2019/10/25 08:51

Sample crash report:
INFO: task syz-executor5:19703 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc8+ #291
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D19416 19703   5503 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
 schedule+0xfe/0x460 kernel/sched/core.c:3517
 io_schedule+0x1c/0x70 kernel/sched/core.c:5140
 wait_on_page_bit_common+0x5b4/0x890 mm/filemap.c:1100
 __lock_page+0x112/0x170 mm/filemap.c:1273
 lock_page include/linux/pagemap.h:483 [inline]
 pagecache_get_page+0x89f/0xf00 mm/filemap.c:1554
 grab_cache_page_write_begin+0x75/0xa0 mm/filemap.c:3089
 block_write_begin+0xae/0x370 fs/buffer.c:2071
 blkdev_write_begin+0x3c/0x50 fs/block_dev.c:585
 generic_perform_write+0x3aa/0x6a0 mm/filemap.c:3139
 __generic_file_write_iter+0x26e/0x630 mm/filemap.c:3264
 blkdev_write_iter+0x23d/0x450 fs/block_dev.c:1916
 call_write_iter include/linux/fs.h:1808 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x6b8/0x9f0 fs/read_write.c:487
 vfs_write+0x1fc/0x560 fs/read_write.c:549
 ksys_write+0x101/0x260 fs/read_write.c:598
 __do_sys_write fs/read_write.c:610 [inline]
 __se_sys_write fs/read_write.c:607 [inline]
 __x64_sys_write+0x73/0xb0 fs/read_write.c:607
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: 83 c4 18 c3 e8 d8 64 00 00 48 8b 04 24 48 8b 4c 24 08 48 89 01 e8 d7 2d fc ff e8 22 7a fc ff b8 02 00 00 00 48 8d 0d 2a 60 09 <01> 87 01 8b 05 22 60 09 01 83 f8 01 0f 85 8a 00 00 00 b8 01 00 00
RSP: 002b:00007f756f45ac78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
RDX: 0000000000000002 RSI: 0000000020000540 RDI: 0000000000000005
RBP: 000000000072bf00 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f756f45b6d4
R13: 00000000004cb700 R14: 00000000004d8dc0 R15: 00000000ffffffff
INFO: task syz-executor5:19715 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc8+ #291
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D22376 19715   5503 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
 schedule+0xfe/0x460 kernel/sched/core.c:3517
 io_schedule+0x1c/0x70 kernel/sched/core.c:5140
 bit_wait_io+0xf/0x90 kernel/sched/wait_bit.c:207
 __wait_on_bit+0xb3/0x130 kernel/sched/wait_bit.c:48
 out_of_line_wait_on_bit+0x213/0x3c0 kernel/sched/wait_bit.c:63
 wait_on_bit_io include/linux/wait_bit.h:101 [inline]
 __wait_on_buffer fs/buffer.c:118 [inline]
 wait_on_buffer include/linux/buffer_head.h:354 [inline]
 __block_write_begin_int+0xa96/0x1d90 fs/buffer.c:2004
 __block_write_begin fs/buffer.c:2016 [inline]
 block_write_begin+0xda/0x370 fs/buffer.c:2075
 blkdev_write_begin+0x3c/0x50 fs/block_dev.c:585
 generic_perform_write+0x3aa/0x6a0 mm/filemap.c:3139
 __generic_file_write_iter+0x26e/0x630 mm/filemap.c:3264
 blkdev_write_iter+0x23d/0x450 fs/block_dev.c:1916
 call_write_iter include/linux/fs.h:1808 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x6b8/0x9f0 fs/read_write.c:487
 vfs_write+0x1fc/0x560 fs/read_write.c:549
 ksys_write+0x101/0x260 fs/read_write.c:598
 __do_sys_write fs/read_write.c:610 [inline]
 __se_sys_write fs/read_write.c:607 [inline]
 __x64_sys_write+0x73/0xb0 fs/read_write.c:607
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: 83 c4 18 c3 e8 d8 64 00 00 48 8b 04 24 48 8b 4c 24 08 48 89 01 e8 d7 2d fc ff e8 22 7a fc ff b8 02 00 00 00 48 8d 0d 2a 60 09 <01> 87 01 8b 05 22 60 09 01 83 f8 01 0f 85 8a 00 00 00 b8 01 00 00
RSP: 002b:00007f756f439c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
RDX: 0000000000000002 RSI: 0000000020000100 RDI: 0000000000000005
RBP: 000000000072bfa0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f756f43a6d4
R13: 00000000004cb700 R14: 00000000004d8dc0 R15: 00000000ffffffff
INFO: task syz-executor5:19727 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc8+ #291
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D19336 19727   5503 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
 schedule+0xfe/0x460 kernel/sched/core.c:3517
 io_schedule+0x1c/0x70 kernel/sched/core.c:5140
 wait_on_page_bit_common+0x5b4/0x890 mm/filemap.c:1100
 __lock_page+0x112/0x170 mm/filemap.c:1273
 lock_page include/linux/pagemap.h:483 [inline]
 pagecache_get_page+0x89f/0xf00 mm/filemap.c:1554
 grab_cache_page_write_begin+0x75/0xa0 mm/filemap.c:3089
 block_write_begin+0xae/0x370 fs/buffer.c:2071
 blkdev_write_begin+0x3c/0x50 fs/block_dev.c:585
 generic_perform_write+0x3aa/0x6a0 mm/filemap.c:3139
 __generic_file_write_iter+0x26e/0x630 mm/filemap.c:3264
 blkdev_write_iter+0x23d/0x450 fs/block_dev.c:1916
 call_write_iter include/linux/fs.h:1808 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x6b8/0x9f0 fs/read_write.c:487
 vfs_write+0x1fc/0x560 fs/read_write.c:549
 ksys_write+0x101/0x260 fs/read_write.c:598
 __do_sys_write fs/read_write.c:610 [inline]
 __se_sys_write fs/read_write.c:607 [inline]
 __x64_sys_write+0x73/0xb0 fs/read_write.c:607
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: 83 c4 18 c3 e8 d8 64 00 00 48 8b 04 24 48 8b 4c 24 08 48 89 01 e8 d7 2d fc ff e8 22 7a fc ff b8 02 00 00 00 48 8d 0d 2a 60 09 <01> 87 01 8b 05 22 60 09 01 83 f8 01 0f 85 8a 00 00 00 b8 01 00 00
RSP: 002b:00007f756f418c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
RDX: 0000000000000002 RSI: 0000000020000100 RDI: 0000000000000003
RBP: 000000000072c040 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f756f4196d4
R13: 00000000004cb700 R14: 00000000004d8dc0 R15: 00000000ffffffff
INFO: task syz-executor5:19777 blocked for more than 140 seconds.
      Not tainted 4.19.0-rc8+ #291
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D24512 19777   5503 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2825 [inline]
 __schedule+0x86c/0x1ed0 kernel/sched/core.c:3473
 schedule+0xfe/0x460 kernel/sched/core.c:3517
 io_schedule+0x1c/0x70 kernel/sched/core.c:5140
 wait_on_page_bit_common+0x5b4/0x890 mm/filemap.c:1100
 __lock_page+0x112/0x170 mm/filemap.c:1273
 lock_page include/linux/pagemap.h:483 [inline]
 pagecache_get_page+0x89f/0xf00 mm/filemap.c:1554
 grab_cache_page_write_begin+0x75/0xa0 mm/filemap.c:3089
 block_write_begin+0xae/0x370 fs/buffer.c:2071
 blkdev_write_begin+0x3c/0x50 fs/block_dev.c:585
 generic_perform_write+0x3aa/0x6a0 mm/filemap.c:3139
 __generic_file_write_iter+0x26e/0x630 mm/filemap.c:3264
 blkdev_write_iter+0x23d/0x450 fs/block_dev.c:1916
 call_write_iter include/linux/fs.h:1808 [inline]
 new_sync_write fs/read_write.c:474 [inline]
 __vfs_write+0x6b8/0x9f0 fs/read_write.c:487
 vfs_write+0x1fc/0x560 fs/read_write.c:549
 ksys_write+0x101/0x260 fs/read_write.c:598
 __do_sys_write fs/read_write.c:610 [inline]
 __se_sys_write fs/read_write.c:607 [inline]
 __x64_sys_write+0x73/0xb0 fs/read_write.c:607
 do_syscall_64+0x1b9/0x820 arch/x86/entry/common.c:290
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x457569
Code: Bad RIP value.
RSP: 002b:00007f756f3f7c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 0000000000457569
RDX: 0000000000000002 RSI: 0000000020000540 RDI: 0000000000000003
RBP: 000000000072c0e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f756f3f86d4
R13: 00000000004cb700 R14: 00000000004d8dc0 R15: 00000000ffffffff

Showing all locks held in the system:
1 lock held by khungtaskd/982:
 #0: 000000006d1d1811 (rcu_read_lock){....}, at: debug_show_all_locks+0xd0/0x424 kernel/locking/lockdep.c:4435
1 lock held by rsyslogd/5229:
 #0: 000000008aa16a96 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x1bb/0x200 fs/file.c:766
2 locks held by getty/5319:
 #0: 000000006c0ba8b5 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 000000003c86aa17 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5320:
 #0: 0000000057bb7933 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000070f5340 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5321:
 #0: 00000000578f77e0 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 0000000091272a91 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5322:
 #0: 000000000eb5a258 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000a34cc00e (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5323:
 #0: 00000000edb91c3a (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000ca521f16 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5324:
 #0: 000000001774e32c (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000eea9fbca (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140
2 locks held by getty/5325:
 #0: 00000000499274e8 (&tty->ldisc_sem){++++}, at: ldsem_down_read+0x32/0x40 drivers/tty/tty_ldsem.c:353
 #1: 00000000af38afd4 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x335/0x1ce0 drivers/tty/n_tty.c:2140

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

NMI backtrace for cpu 0
CPU: 0 PID: 982 Comm: khungtaskd Not tainted 4.19.0-rc8+ #291
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+0x1c4/0x2b4 lib/dump_stack.c:113
 nmi_cpu_backtrace.cold.3+0x63/0xa2 lib/nmi_backtrace.c:101
 nmi_trigger_cpumask_backtrace+0x1b3/0x1ed lib/nmi_backtrace.c:62
 arch_trigger_cpumask_backtrace+0x14/0x20 arch/x86/kernel/apic/hw_nmi.c:38
 trigger_all_cpu_backtrace include/linux/nmi.h:144 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:204 [inline]
 watchdog+0xb3e/0x1050 kernel/hung_task.c:265
 kthread+0x35a/0x420 kernel/kthread.c:246
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:413
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:57

Crashes (144):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-root 2018/10/19 18:29 upstream 91b15613ce7f 9aba67b5 .config log report
ci-upstream-kasan-gce 2018/04/13 06:29 upstream c17b0aadb7d8 eb2295de .config log report
ci-upstream-kasan-gce 2018/04/10 14:34 upstream c18bb396d3d2 8e873e9d .config log report
ci-upstream-kasan-gce 2018/04/10 04:11 upstream fd40ffc72e2f b9f65507 .config log report
ci-upstream-kasan-gce 2018/04/09 12:31 upstream 3fd14cdcc05a f13fb445 .config log report
ci-upstream-kasan-gce 2018/04/06 07:15 upstream e02d37bf55a9 a932eae6 .config log report
ci-upstream-kasan-gce 2018/04/05 03:07 upstream 3e968c9f1401 676bd07e .config log report
ci-upstream-kasan-gce 2018/04/04 20:12 upstream 17dec0a94915 676bd07e .config log report
ci-upstream-kasan-gce-root 2018/04/04 06:49 upstream f2d285669aae 676bd07e .config log report
ci-upstream-kasan-gce 2018/04/02 07:30 upstream 0adb32858b0b dc889257 .config log report
ci-upstream-kasan-gce 2018/04/01 03:21 upstream 10b84daddbec 0174c6c8 .config log report
ci-upstream-kasan-gce 2018/03/31 21:54 upstream 10b84daddbec 0174c6c8 .config log report
ci-upstream-kasan-gce-root 2018/03/29 08:35 upstream a2601d78b77a bf5e585c .config log report
ci-upstream-kasan-gce-root 2018/03/28 12:49 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-root 2018/03/28 10:50 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-root 2018/03/28 05:34 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-root 2018/03/26 17:02 upstream 3eb2ce825ea1 0ca7878b .config log report
ci-upstream-kasan-gce 2018/03/24 18:01 upstream bcfc1f455466 2e9d9054 .config log report
ci-upstream-kasan-gce 2018/03/04 22:39 upstream e64b9562ba28 2c6f473e .config log report
ci-upstream-kasan-gce 2018/03/03 21:01 upstream 5fbdefcf685d 2c6f473e .config log report
ci-upstream-kasan-gce 2018/02/25 21:48 upstream 3664ce2d9309 9fe8aa42 .config log report
ci-upstream-kasan-gce 2018/02/04 20:54 upstream 617aebe6a97e a1bc9d40 .config log report
ci-upstream-kasan-gce 2018/02/03 23:01 upstream 23c35f48f5fb 632a8c2c .config log report
ci-upstream-kasan-gce 2018/02/03 17:03 upstream b89e32ccd1be 632a8c2c .config log report
ci-upstream-kasan-gce 2018/01/29 23:58 upstream d8a5b80568a9 08d47756 .config log report
ci-upstream-kasan-gce 2018/01/28 10:31 upstream c4e0ca7fa241 08d47756 .config log report
ci-upstream-kasan-gce-386 2018/04/08 09:32 upstream f2d285669aae 66f22a7f .config log report
ci-upstream-kasan-gce-386 2018/04/08 05:43 upstream f2d285669aae 66f22a7f .config log report
ci-upstream-kasan-gce-386 2018/04/03 06:09 upstream 86bbbebac193 676bd07e .config log report
ci-upstream-kasan-gce-386 2018/04/03 04:11 upstream 86bbbebac193 676bd07e .config log report
ci-upstream-kasan-gce-386 2018/03/27 14:14 upstream 3eb2ce825ea1 bf5e585c .config log report
ci-upstream-kasan-gce-386 2018/03/27 07:39 upstream 3eb2ce825ea1 0ca7878b .config log report
ci-upstream-kasan-gce-386 2018/03/18 03:13 upstream 8f5fd927c3a7 08dacaa0 .config log report
ci-upstream-kasan-gce-386 2018/02/26 18:24 upstream 4a3928c6f8a5 9fe8aa42 .config log report
ci-upstream-kasan-gce-386 2018/02/26 15:12 upstream 4a3928c6f8a5 9fe8aa42 .config log report
ci-upstream-kasan-gce-386 2018/02/08 04:02 upstream 581e400ff935 9fb5ec43 .config log report
ci-upstream-kasan-gce-386 2018/02/04 23:15 upstream 617aebe6a97e a1bc9d40 .config log report
ci-upstream-kasan-gce-386 2018/01/21 00:18 upstream 24b61240471a fbbdcd92 .config log report
ci-upstream-linux-next-kasan-gce-root 2018/07/09 05:54 linux-next 526674536360 f25e5770 .config log report
ci-upstream-next-kasan-gce 2018/01/20 05:44 linux-next 761914dd2975 fbbdcd92 .config log report
ci-upstream-mmots-kasan-gce 2018/01/18 21:52 mmots ce3c209f6733 161c1d64 .config log report
ci-upstream-mmots-kasan-gce 2018/01/18 16:19 mmots ce3c209f6733 56cc113a .config log report
ci-upstream-mmots-kasan-gce 2018/01/18 16:07 mmots ce3c209f6733 56cc113a .config log report
ci-upstream-mmots-kasan-gce 2018/01/18 07:56 mmots ce3c209f6733 b8970f31 .config log report