[v6.1] INFO: task hung in filemap_fault

5 views
Skip to first unread message

syzbot

unread,
May 8, 2023, 8:32:58 AM5/8/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ca48fc16c493 Linux 6.1.27
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a3394c280000
kernel config: https://syzkaller.appspot.com/x/.config?x=aea4bb7802570997
dashboard link: https://syzkaller.appspot.com/bug?extid=4e238bd085509afee670
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ec11c1903c52/disk-ca48fc16.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8ce41c1ad391/vmlinux-ca48fc16.xz
kernel image: https://storage.googleapis.com/syzbot-assets/affba5631cad/Image-ca48fc16.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4e238b...@syzkaller.appspotmail.com

INFO: task syz-executor.5:25941 blocked for more than 143 seconds.
Not tainted 6.1.27-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:0 pid:25941 ppid:4269 flags:0x00000009
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+0x68/0x2d8 kernel/locking/rwsem.c:1261
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0x68/0x78 kernel/locking/rwsem.c:1522
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
filemap_fault+0x744/0xf7c mm/filemap.c:3143
__do_fault+0x11c/0x3d8 mm/memory.c:4212
do_read_fault mm/memory.c:4563 [inline]
do_fault mm/memory.c:4692 [inline]
handle_pte_fault mm/memory.c:4964 [inline]
__handle_mm_fault mm/memory.c:5106 [inline]
handle_mm_fault+0x1f68/0x3e9c mm/memory.c:5227
faultin_page mm/gup.c:1009 [inline]
__get_user_pages+0x3b0/0x968 mm/gup.c:1233
populate_vma_page_range+0x1fc/0x2a0 mm/gup.c:1590
__mm_populate+0x240/0x3d8 mm/gup.c:1704
mm_populate include/linux/mm.h:2771 [inline]
vm_mmap_pgoff+0x1fc/0x2b4 mm/util.c:525
ksys_mmap_pgoff+0x3c8/0x5b0 mm/mmap.c:1457
__do_sys_mmap arch/arm64/kernel/sys.c:28 [inline]
__se_sys_mmap arch/arm64/kernel/sys.c:21 [inline]
__arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21
__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
INFO: task syz-executor.5:25950 blocked for more than 143 seconds.
Not tainted 6.1.27-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:0 pid:25950 ppid:4269 flags:0x00000009
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+0x68/0x2d8 kernel/locking/rwsem.c:1261
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0x68/0x78 kernel/locking/rwsem.c:1522
filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
filemap_fault+0x744/0xf7c mm/filemap.c:3143
__do_fault+0x11c/0x3d8 mm/memory.c:4212
do_read_fault mm/memory.c:4563 [inline]
do_fault mm/memory.c:4692 [inline]
handle_pte_fault mm/memory.c:4964 [inline]
__handle_mm_fault mm/memory.c:5106 [inline]
handle_mm_fault+0x1f68/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
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:367
el1h_64_sync_handler+0x60/0xac arch/arm64/kernel/entry-common.c:427
el1h_64_sync+0x64/0x68 arch/arm64/kernel/entry.S:576
__arch_copy_from_user+0x180/0x230 arch/arm64/lib/copy_template.S:146
snd_rawmidi_write+0x4d8/0x9dc sound/core/rawmidi.c:1618
vfs_write+0x2a4/0x914 fs/read_write.c:582
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__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
INFO: task syz-executor.5:25956 blocked for more than 143 seconds.
Not tainted 6.1.27-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5 state:D stack:0 pid:25956 ppid:4269 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]
blk_ioctl_zeroout block/ioctl.c:182 [inline]
blkdev_common_ioctl+0x1a08/0x26b4 block/ioctl.c:486
blkdev_ioctl+0x380/0xb40 block/ioctl.c:609
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:856
__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: ffff800015764d30 (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: ffff800015765530 (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: ffff800015764b60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by getty/3977:
#0: ffff0000d5efe098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001ca502f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1210 drivers/tty/n_tty.c:2177
5 locks held by syz-executor.3/4282:
2 locks held by syz-executor.4/4285:
2 locks held by kworker/u4:12/9267:
2 locks held by syz-executor.2/17864:
2 locks held by syz-executor.5/25941:
#0: ffff0000d7fe3d48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock include/linux/mmap_lock.h:117 [inline]
#0: ffff0000d7fe3d48 (&mm->mmap_lock){++++}-{3:3}, at: __mm_populate+0x190/0x3d8 mm/gup.c:1683
#1: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#1: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_fault+0x744/0xf7c mm/filemap.c:3143
2 locks held by syz-executor.5/25950:
#0: ffff0000d7fe3d48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_trylock include/linux/mmap_lock.h:136 [inline]
#0: ffff0000d7fe3d48 (&mm->mmap_lock){++++}-{3:3}, at: do_page_fault+0x2dc/0xac4 arch/arm64/mm/fault.c:593
#1: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:811 [inline]
#1: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_fault+0x744/0xf7c mm/filemap.c:3143
1 lock held by syz-executor.5/25956:
#0: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:801 [inline]
#0: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blk_ioctl_zeroout block/ioctl.c:182 [inline]
#0: ffff0000c04a6bd8 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_common_ioctl+0x1a08/0x26b4 block/ioctl.c:486
3 locks held by syz-executor.5/25999:
1 lock held by modprobe/31309:
#0: ffff0001b45c6598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested kernel/sched/core.c:537 [inline]
#0: ffff0001b45c6598 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock kernel/sched/sched.h:1355 [inline]
#0: ffff0001b45c6598 (&rq->__lock){-.-.}-{2:2}, at: rq_lock kernel/sched/sched.h:1645 [inline]
#0: ffff0001b45c6598 (&rq->__lock){-.-.}-{2:2}, at: __schedule+0x2c4/0x1c98 kernel/sched/core.c:6471
1 lock held by modprobe/31319:
2 locks held by syz-executor.3/31321:

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

syzbot

unread,
Sep 9, 2023, 7:34:48 AM9/9/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages