syzbot


INFO: task hung in invalidate_inode_pages2_range

Status: auto-closed as invalid on 2019/02/22 10:34
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+ab6c4860c388a257339a32b72990469cdf26df77@syzkaller.appspotmail.com
First crash: 2317d, last: 2210d
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 INFO: task hung in invalidate_inode_pages2_range 1 476d 476d 0/1 upstream: reported on 2023/01/06 10:24
android-49 INFO: task hung in invalidate_inode_pages2_range 13 2199d 2264d 0/3 auto-closed as invalid on 2019/02/22 15:29
android-44 INFO: task hung in invalidate_inode_pages2_range 3 2241d 2246d 0/2 auto-closed as invalid on 2019/02/22 15:29

Sample crash report:
Buffer I/O error on dev loop0, logical block 16, async page read
INFO: task syz-executor5:16159 blocked for more than 120 seconds.
      Not tainted 4.15.0-rc9+ #282
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor5   D22600 16159   3705 0x00000004
Call Trace:
 context_switch kernel/sched/core.c:2799 [inline]
 __schedule+0x8eb/0x2060 kernel/sched/core.c:3375
 schedule+0xf5/0x430 kernel/sched/core.c:3434
 io_schedule+0x1c/0x70 kernel/sched/core.c:5042
 wait_on_page_bit_common mm/filemap.c:1100 [inline]
 __lock_page+0x574/0x720 mm/filemap.c:1273
 lock_page include/linux/pagemap.h:483 [inline]
 invalidate_inode_pages2_range+0x989/0x1170 mm/truncate.c:706
 generic_file_direct_write+0x339/0x440 mm/filemap.c:3058
 __generic_file_write_iter+0x21f/0x5b0 mm/filemap.c:3221
 blkdev_write_iter+0x207/0x3e0 fs/block_dev.c:1893
 call_write_iter include/linux/fs.h:1772 [inline]
 do_iter_readv_writev+0x525/0x7f0 fs/read_write.c:653
 do_iter_write+0x154/0x540 fs/read_write.c:932
 vfs_iter_write+0x77/0xb0 fs/read_write.c:945
 iter_file_splice_write+0x7db/0xf30 fs/splice.c:749
 do_splice_from fs/splice.c:851 [inline]
 direct_splice_actor+0x125/0x180 fs/splice.c:1018
 splice_direct_to_actor+0x2c1/0x820 fs/splice.c:973
 do_splice_direct+0x29b/0x3c0 fs/splice.c:1061
 do_sendfile+0x5c9/0xe80 fs/read_write.c:1413
 SYSC_sendfile64 fs/read_write.c:1468 [inline]
 SyS_sendfile64+0xbd/0x160 fs/read_write.c:1460
 entry_SYSCALL_64_fastpath+0x29/0xa0
RIP: 0033:0x452f19
RSP: 002b:00007f48a9182c58 EFLAGS: 00000212 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 000000000071bea0 RCX: 0000000000452f19
RDX: 00000000200ddff8 RSI: 0000000000000014 RDI: 0000000000000013
RBP: 00000000000002cc R08: 0000000000000000 R09: 0000000000000000
R10: 0000000100000001 R11: 0000000000000212 R12: 00000000006f33c0
R13: 00000000ffffffff R14: 00007f48a91836d4 R15: 0000000000000000

Showing all locks held in the system:
2 locks held by khungtaskd/745:
 #0:  (rcu_read_lock){....}, at: [<0000000037675379>] check_hung_uninterruptible_tasks kernel/hung_task.c:175 [inline]
 #0:  (rcu_read_lock){....}, at: [<0000000037675379>] watchdog+0x1c5/0xd60 kernel/hung_task.c:249
 #1:  (tasklist_lock){.+.+}, at: [<00000000560ef908>] debug_show_all_locks+0xd3/0x400 kernel/locking/lockdep.c:4464
2 locks held by getty/3633:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3634:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3635:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3636:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3637:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3638:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
2 locks held by getty/3639:
 #0:  (&tty->ldisc_sem){++++}, at: [<00000000a802ea49>] ldsem_down_read+0x37/0x40 drivers/tty/tty_ldsem.c:365
 #1:  (&ldata->atomic_read_lock){+.+.}, at: [<000000009fe4573a>] n_tty_read+0x2ef/0x1a00 drivers/tty/n_tty.c:2131
3 locks held by kworker/u4:6/5513:
 #0:  ((wq_completion)"writeback"){+.+.}, at: [<000000008a2f1294>] process_one_work+0xaaf/0x1b10 kernel/workqueue.c:2084
 #1:  ((work_completion)(&(&wb->dwork)->work)){+.+.}, at: [<00000000bc1414ec>] process_one_work+0xb01/0x1b10 kernel/workqueue.c:2088
 #2:  (&type->s_umount_key#27){++++}, at: [<000000006a407b04>] trylock_super+0x20/0x100 fs/super.c:395

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

NMI backtrace for cpu 1
CPU: 1 PID: 745 Comm: khungtaskd Not tainted 4.15.0-rc9+ #282
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x194/0x257 lib/dump_stack.c:53
 nmi_cpu_backtrace+0x1d2/0x210 lib/nmi_backtrace.c:103
 nmi_trigger_cpumask_backtrace+0x122/0x180 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:138 [inline]
 check_hung_task kernel/hung_task.c:132 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:190 [inline]
 watchdog+0x90c/0xd60 kernel/hung_task.c:249
 kthread+0x33c/0x400 kernel/kthread.c:238
 ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:541
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-rc9+ #282
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:smp_reschedule_interrupt+0x0/0x670
RSP: 0018:ffff8801db207ff0 EFLAGS: 00000046
RAX: dffffc0000000000 RBX: 1ffffffff0d00f8a RCX: 0000000000000000
RDX: 1ffffffff0d19190 RSI: 0000000000000001 RDI: ffffffff86807b88
RBP: ffffffff86807b89 R08: ffffffff86670ae0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: ffffffff86807cf0 R14: ffffffff87038820 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8801db200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000954000 CR3: 0000000006822003 CR4: 00000000001606f0
Call Trace:
 <IRQ>
 </IRQ>
Code: ff ff 4c 89 e7 e8 61 e5 26 fc e9 5c fa ff ff e8 57 e5 26 fc e9 30 fa ff ff e8 4d e5 26 fc e9 5a fd ff ff 90 90 90 90 90 90 90 90 <55> 48 ba 00 00 00 00 00 fc ff df 48 c7 c7 60 11 67 86 48 89 e5 

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2018/01/27 07:55 upstream c4e0ca7fa241 1d18b112 .config console log report ci-upstream-kasan-gce
2018/01/17 08:42 upstream 41aa5e5d712b a46e5318 .config console log report ci-upstream-kasan-gce
2018/01/17 05:39 upstream 41aa5e5d712b a46e5318 .config console log report ci-upstream-kasan-gce
2018/04/08 01:46 upstream f2d285669aae 66f22a7f .config console log report ci-upstream-kasan-gce-386
2017/12/28 00:11 linux-next 0e08c463db38 7d240098 .config console log report ci-upstream-next-kasan-gce
2017/12/22 13:15 linux-next 0e08c463db38 81fe66b4 .config console log report ci-upstream-next-kasan-gce
* Struck through repros no longer work on HEAD.