[v5.15] INFO: task hung in page_cache_ra_unbounded

0 views
Skip to first unread message

syzbot

unread,
Jan 25, 2024, 1:23:24 PMJan 25
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: ddcaf4999061 Linux 5.15.147
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13b400a7e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c65db3d25098c3c
dashboard link: https://syzkaller.appspot.com/bug?extid=621fd4619540ebd8d0b1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fe87fb57528f/disk-ddcaf499.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f64608a2759c/vmlinux-ddcaf499.xz
kernel image: https://storage.googleapis.com/syzbot-assets/84cae5bc6ed5/bzImage-ddcaf499.xz

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

INFO: task syz-executor.3:15564 blocked for more than 143 seconds.
Not tainted 5.15.147-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:26200 pid:15564 ppid: 3535 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1047
__down_read_common kernel/locking/rwsem.c:1231 [inline]
__down_read kernel/locking/rwsem.c:1244 [inline]
down_read+0x9a/0x2e0 kernel/locking/rwsem.c:1490
filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
page_cache_ra_unbounded+0x1a6/0x930 mm/readahead.c:195
do_sync_mmap_readahead+0x610/0x800 mm/filemap.c:2996
filemap_fault+0x77a/0x1470 mm/filemap.c:3089
__do_fault+0x139/0x340 mm/memory.c:3898
do_cow_fault mm/memory.c:4263 [inline]
do_fault mm/memory.c:4364 [inline]
handle_pte_fault mm/memory.c:4621 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x30da/0x5950 mm/memory.c:4854
do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x7fe9f4dee551
RSP: 002b:00007ffd1cf3bf30 EFLAGS: 00010246
RAX: 00000000200004c0 RBX: 0000000000000004 RCX: 0000000000000000
RDX: 0000000000000080 RSI: 0000000000000000 RDI: 00005555556d1360
RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
R10: 00007ffd1cf68080 R11: 0000000000026f5e R12: 00007fe9f49c3638
R13: fffffffffffffffe R14: 00007fe9f49c3000 R15: 00007fe9f49c3640
</TASK>
INFO: task syz-executor.3:15565 blocked for more than 145 seconds.
Not tainted 5.15.147-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.3 state:D stack:26464 pid:15565 ppid: 3535 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x12c4/0x45b0 kernel/sched/core.c:6376
schedule+0x11b/0x1f0 kernel/sched/core.c:6459
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6518
rwsem_down_read_slowpath+0x605/0xb40 kernel/locking/rwsem.c:1047
__down_read_common kernel/locking/rwsem.c:1231 [inline]
__down_read kernel/locking/rwsem.c:1244 [inline]
down_read+0x9a/0x2e0 kernel/locking/rwsem.c:1490
filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
page_cache_ra_unbounded+0x1a6/0x930 mm/readahead.c:195
do_sync_mmap_readahead+0x610/0x800 mm/filemap.c:2996
filemap_fault+0x77a/0x1470 mm/filemap.c:3089
__do_fault+0x139/0x340 mm/memory.c:3898
do_cow_fault mm/memory.c:4263 [inline]
do_fault mm/memory.c:4364 [inline]
handle_pte_fault mm/memory.c:4621 [inline]
__handle_mm_fault mm/memory.c:4756 [inline]
handle_mm_fault+0x30da/0x5950 mm/memory.c:4854
do_user_addr_fault arch/x86/mm/fault.c:1397 [inline]
handle_page_fault arch/x86/mm/fault.c:1485 [inline]
exc_page_fault+0x271/0x740 arch/x86/mm/fault.c:1541
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0010:copy_user_enhanced_fast_string+0xe/0x40 arch/x86/lib/copy_user_64.S:206
Code: 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 f3 a4 31 c0 0f 01 ca c3 0f 1f 80 00 00 00 00 0f 01 cb 83 fa 40 0f 82 70 ff ff ff 89 d1 <f3> a4 31 c0 0f 01 ca c3 66 2e 0f 1f 84 00 00 00 00 00 89 d1 83 f8
RSP: 0000:ffffc90006527c10 EFLAGS: 00050246
RAX: ffffffff84076101 RBX: 0000000020002240 RCX: 0000000000000040
RDX: 0000000000000040 RSI: ffff88814700ed80 RDI: 0000000020002200
RBP: 0000000000000040 R08: dffffc0000000000 R09: ffffed1028e01db8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000040
R13: 00007ffffffff000 R14: ffff88814700ed80 R15: 0000000020002200
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_to_user arch/x86/include/asm/uaccess_64.h:58 [inline]
_copy_to_user+0xef/0x130 lib/usercopy.c:40
copy_to_user include/linux/uaccess.h:200 [inline]
rng_dev_read+0x2e9/0x5a0 drivers/char/hw_random/core.c:252
do_iter_read+0x4ca/0x760 fs/read_write.c:792
vfs_readv fs/read_write.c:910 [inline]
do_preadv+0x211/0x350 fs/read_write.c:1002
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fe9f4e3fda9
RSP: 002b:00007fe9f33c10c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000127
RAX: ffffffffffffffda RBX: 00007fe9f4f6ef80 RCX: 00007fe9f4e3fda9
RDX: 0000000000000001 RSI: 0000000020001880 RDI: 0000000000000004
RBP: 00007fe9f4e8c47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fe9f4f6ef80 R15: 00007ffd1cf3be88
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c91f220 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
1 lock held by hwrng/903:
#0: ffffffff8cff8368 (reading_mutex){+.+.}-{3:3}, at: hwrng_fillfn+0xdd/0x280 drivers/char/hw_random/core.c:436
1 lock held by klogd/2953:
#0: ffff8880b9a39718 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xa8/0x140 kernel/sched/core.c:483
2 locks held by getty/3271:
#0: ffff88814af83098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002bab2e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6af/0x1db0 drivers/tty/n_tty.c:2158
3 locks held by kworker/0:2/9464:
#0: ffff888011c70d38 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x78a/0x10c0 kernel/workqueue.c:2283
#1: ffffc9000566fd20 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x7d0/0x10c0 kernel/workqueue.c:2285
#2: ffffffff8d9da3c8 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
1 lock held by syz-executor.1/15500:
1 lock held by syz-executor.3/15564:
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: page_cache_ra_unbounded+0x1a6/0x930 mm/readahead.c:195
2 locks held by syz-executor.3/15565:
#0: ffffffff8cff8368 (reading_mutex){+.+.}-{3:3}, at: rng_dev_read+0xee/0x5a0 drivers/char/hw_random/core.c:225
#1: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:842 [inline]
#1: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: page_cache_ra_unbounded+0x1a6/0x930 mm/readahead.c:195
1 lock held by syz-executor.1/15671:
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
2 locks held by kworker/u4:2/15945:
1 lock held by syz-executor.1/16232:
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:832 [inline]
#0: ffff88801b474438 (mapping.invalidate_lock#2){++++}-{3:3}, at: blkdev_fallocate+0x25e/0x4e0 block/fops.c:600
2 locks held by syz-executor.1/16523:
#0: ffffffff8d9da3c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d9da3c8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x94c/0xee0 net/core/rtnetlink.c:5627
#1: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:290 [inline]
#1: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x280/0x740 kernel/rcu/tree_exp.h:845
2 locks held by syz-executor.3/16641:
2 locks held by syz-executor.3/16649:
#0: ffff88807b2540c8 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x1d4/0xcf0 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3870
#1: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c9237e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x350/0x740 kernel/rcu/tree_exp.h:845
1 lock held by syz-executor.4/16640:
1 lock held by syz-executor.5/16653:
#0: ffffffff8d9da3c8 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x598/0xf60 net/core/dev_ioctl.c:611
1 lock held by syz-executor.5/16655:
#0: ffffffff8d9da3c8 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x598/0xf60 net/core/dev_ioctl.c:611
5 locks held by syz-executor.2/16658:

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 5.15.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
nmi_cpu_backtrace+0x46a/0x4a0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x181/0x2a0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:210 [inline]
watchdog+0xe72/0xeb0 kernel/hung_task.c:295
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 0 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 0 skipped: idling at acpi_safe_halt drivers/acpi/processor_idle.c:109 [inline]
NMI backtrace for cpu 0 skipped: idling at acpi_idle_do_entry+0x10f/0x340 drivers/acpi/processor_idle.c:570


---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages