syzbot


INFO: task hung in filemap_fault

Status: auto-obsoleted due to no activity on 2023/09/09 11:34
Reported-by: syzbot+4e238bd085509afee670@syzkaller.appspotmail.com
First crash: 577d, last: 553d
Similar bugs (10)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in filemap_fault (3) mm 1 1095d 1095d 0/28 closed as invalid on 2022/02/08 09:40
upstream INFO: task hung in filemap_fault (5) mm fs 12 539d 917d 0/28 auto-obsoleted due to no activity on 2023/09/13 22:48
linux-5.15 INFO: task hung in filemap_fault 1 472d 472d 0/3 auto-obsoleted due to no activity on 2023/11/29 22:47
upstream INFO: task hung in filemap_fault mm 24 2523d 2544d 0/28 closed as invalid on 2018/02/13 19:52
android-44 INFO: task hung in filemap_fault 3 2454d 2455d 0/2 auto-closed as invalid on 2019/02/22 14:09
upstream INFO: task hung in filemap_fault (6) mm 183 10d 149d 0/28 upstream: reported on 2024/07/09 16:36
android-49 INFO: task hung in filemap_fault 4 2346d 2393d 0/3 auto-closed as invalid on 2019/02/22 14:49
upstream INFO: task hung in filemap_fault (2) mm 5 2236d 2441d 0/28 auto-closed as invalid on 2019/04/20 06:20
linux-5.15 INFO: task hung in filemap_fault (2) 1 101d 101d 0/3 auto-obsoleted due to no activity on 2024/12/04 10:30
upstream INFO: task hung in filemap_fault (4) mm 1 1013d 1013d 0/28 auto-closed as invalid on 2022/05/27 12:14

Sample crash report:
INFO: task syz-executor.4:3512 blocked for more than 143 seconds.
      Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:0     pid:3512  ppid:4272   flags:0x00000001
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6689
 rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
 __down_read_common kernel/locking/rwsem.c:1261 [inline]
 __down_read kernel/locking/rwsem.c:1274 [inline]
 down_read+0xac/0x308 kernel/locking/rwsem.c:1522
 filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
 filemap_fault+0x58c/0xf7c mm/filemap.c:3128
 __do_fault+0x11c/0x3d8 mm/memory.c:4212
 do_shared_fault mm/memory.c:4618 [inline]
 do_fault mm/memory.c:4696 [inline]
 handle_pte_fault mm/memory.c:4964 [inline]
 __handle_mm_fault mm/memory.c:5106 [inline]
 handle_mm_fault+0x18e4/0x3e9c mm/memory.c:5227
 __do_page_fault arch/arm64/mm/fault.c:512 [inline]
 do_page_fault+0x634/0xac4 arch/arm64/mm/fault.c:612
 do_translation_fault+0x94/0xc8 arch/arm64/mm/fault.c:695
 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:831
 el0_da+0x70/0x184 arch/arm64/kernel/entry-common.c:515
 el0t_64_sync_handler+0xcc/0xf0 arch/arm64/kernel/entry-common.c:658
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
INFO: task syz-executor.4:3526 blocked for more than 143 seconds.
      Not tainted 6.1.31-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4  state:D stack:0     pid:3526  ppid:4272   flags:0x00000001
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
 __down_write_common kernel/locking/rwsem.c:1314 [inline]
 __down_write kernel/locking/rwsem.c:1323 [inline]
 down_write+0x84/0x88 kernel/locking/rwsem.c:1574
 filemap_invalidate_lock include/linux/fs.h:801 [inline]
 blkdev_fallocate+0x1d4/0x340 block/fops.c:656
 vfs_fallocate+0x478/0x5b4 fs/open.c:323
 ksys_fallocate fs/open.c:346 [inline]
 __do_sys_fallocate fs/open.c:354 [inline]
 __se_sys_fallocate fs/open.c:352 [inline]
 __arm64_sys_fallocate+0xc0/0x110 fs/open.c:352
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffff800015794e70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/13:
 #0: ffff800015795670 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/28:
 #0: ffff800015794ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3973:
 #0: ffff0000d62fb098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff80001ba302f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
2 locks held by kworker/u4:9/5388:
2 locks held by syz-executor.4/3512:
 #0: ffff0000c9819f48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
 #0: ffff0000c9819f48 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x2dc/0xac4 arch/arm64/mm/fault.c:593
 #1: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
 #1: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_fault+0x58c/0xf7c mm/filemap.c:3128
3 locks held by syz-executor.4/3516:
1 lock held by syz-executor.4/3526:
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor.3/3668:
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656
1 lock held by syz-executor.3/3746:
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
 #0: ffff0000c05113d8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x1d4/0x340 block/fops.c:656

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


Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/06/01 11:33 linux-6.1.y d2869ace6eeb babc4389 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in filemap_fault
2023/05/08 12:32 linux-6.1.y ca48fc16c493 90c93c40 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in filemap_fault
* Struck through repros no longer work on HEAD.