[v6.1] INFO: rcu detected stall in shmem_fault

0 views
Skip to first unread message

syzbot

unread,
Jun 7, 2024, 6:17:28 AMJun 7
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16cea364980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=04d977c0209629383d45
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/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P4326/1:b..l
(detected by 1, t=10502 jiffies, g=12953, q=22 ncpus=2)
task:syz-executor.4 state:R running task stack:24664 pid:4326 ppid:3570 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:lock_is_held_type+0x137/0x180
Code: 75 40 48 c7 04 24 00 00 00 00 9c 8f 04 24 f7 04 24 00 02 00 00 75 46 41 f7 c4 00 02 00 00 74 01 fb 65 48 8b 04 25 28 00 00 00 <48> 3b 44 24 08 75 3c 89 e8 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f
RSP: 0000:ffffc900139ff300 EFLAGS: 00000206
RAX: fd050f6839f75400 RBX: 0000000000000002 RCX: 0000000080000000
RDX: dffffc0000000000 RSI: ffffffff8aec1340 RDI: ffffffff8b3d45e0
RBP: 0000000000000000 R08: dffffc0000000000 R09: fffffbfff2093845
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000246
R13: ffff888025559dc0 R14: 00000000ffffffff R15: ffffffff8d1534a8
lock_is_held include/linux/lockdep.h:283 [inline]
task_css include/linux/cgroup.h:509 [inline]
mem_cgroup_from_task+0x5e/0x110 mm/memcontrol.c:985
get_mem_cgroup_from_mm+0xd3/0x290 mm/memcontrol.c:1038
__mem_cgroup_charge+0x12/0x80 mm/memcontrol.c:6919
mem_cgroup_charge include/linux/memcontrol.h:672 [inline]
shmem_add_to_page_cache+0xaa6/0x1e60 mm/shmem.c:708
shmem_get_folio_gfp+0x164e/0x3470 mm/shmem.c:1971
shmem_fault+0x235/0x9c0 mm/shmem.c:2156
__do_fault+0x136/0x4f0 mm/memory.c:4261
do_read_fault mm/memory.c:4612 [inline]
do_fault mm/memory.c:4741 [inline]
handle_pte_fault mm/memory.c:5013 [inline]
__handle_mm_fault mm/memory.c:5155 [inline]
handle_mm_fault+0x3412/0x5340 mm/memory.c:5276
faultin_page mm/gup.c:1009 [inline]
__get_user_pages+0x4f3/0x1190 mm/gup.c:1233
populate_vma_page_range+0x217/0x2b0 mm/gup.c:1590
__mm_populate+0x275/0x440 mm/gup.c:1704
mm_populate include/linux/mm.h:2797 [inline]
vm_mmap_pgoff+0x22b/0x2d0 mm/util.c:525
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fd20dc7cf69
RSP: 002b:00007fd20ea590c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007fd20ddb3f80 RCX: 00007fd20dc7cf69
RDX: b635773f06ebbeee RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 00007fd20dcda6fe R08: ffffffffffffffff R09: 0000000000000000
R10: 0000000000008031 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007fd20ddb3f80 R15: 00007fff78397878
</TASK>
rcu: rcu_preempt kthread starved for 10538 jiffies! g12953 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=0
rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
rcu: RCU grace-period kthread stack dump:
task:rcu_preempt state:R running task stack:25816 pid:16 ppid:2 flags:0x00004000
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x142d/0x4550 kernel/sched/core.c:6558
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:kasan_check_range+0x3/0x290 mm/kasan/generic.c:188
Code: 48 89 c7 e8 8f b9 a9 08 31 c0 c3 0f 0b b8 ea ff ff ff c3 0f 0b b8 ea ff ff ff c3 cc cc cc cc cc cc cc cc cc cc cc cc 55 41 57 <41> 56 53 b0 01 48 85 f6 0f 84 9a 01 00 00 48 89 fd 48 01 f5 0f 82
RSP: 0018:ffffc90000157b80 EFLAGS: 00000246
RAX: 0000000000000001 RBX: 1ffff11027fd5b28 RCX: ffffffff8a938926
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88813fead940
RBP: ffffc90000157cb0 R08: dffffc0000000000 R09: ffffed1017307541
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88813fead940
R13: 1ffff9200002af78 R14: ffff88813feaebb8 R15: dffffc0000000000
instrument_atomic_read include/linux/instrumented.h:72 [inline]
_test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline]
test_ti_thread_flag include/linux/thread_info.h:118 [inline]
need_resched include/linux/sched.h:2231 [inline]
schedule+0xd6/0x180 kernel/sched/core.c:6636
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1965
rcu_gp_fqs_loop+0x2d2/0x1150 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3b0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:update_rq_clock+0x3/0x870 kernel/sched/core.c:729
Code: 8a 44 89 f1 80 e1 07 80 c1 03 38 c1 7c cb 4c 89 f7 e8 31 ac 83 00 eb c1 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 41 57 <41> 56 41 55 41 54 53 48 83 ec 30 49 89 fe 48 c7 c0 24 be 73 8e 48
RSP: 0018:ffffc90000147ae8 EFLAGS: 00000002
RAX: 0000000000000000 RBX: ffff8880b983aa00 RCX: 1ffff11017307688
RDX: 1ffffffff1fd3e00 RSI: ffffffff8aec1340 RDI: ffff8880b983aa00
RBP: ffffc90000147cb0 R08: ffffffff8fe9f000 R09: ffffffff8fe9f008
R10: ffffffff8fe9f018 R11: ffffffff8fe9f010 R12: 0000000000000001
R13: 1ffff92000028f9c R14: dffffc0000000000 R15: 00000000000053fe
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd20ea37f00 CR3: 0000000077dd6000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<TASK>
__schedule+0x42b/0x4550 kernel/sched/core.c:6480
preempt_schedule_irq+0xf7/0x1c0 kernel/sched/core.c:6870
irqentry_exit+0x53/0x80 kernel/entry/common.c:439
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:27 [inline]
RIP: 0010:preempt_count_add+0x32/0x180 kernel/sched/core.c:5703
Code: c7 c0 60 41 c9 91 48 c1 e8 03 49 bf 00 00 00 00 00 fc ff df 42 0f b6 04 38 84 c0 0f 85 e2 00 00 00 83 3d e0 ee 6a 10 00 75 07 <65> 8b 05 bf 1c a4 7e 65 01 1d b8 1c a4 7e 48 c7 c0 60 41 c9 91 48
RSP: 0018:ffffc90000147e30 EFLAGS: 00000246
RAX: 0000000000000004 RBX: 0000000000000001 RCX: ffffffff91c94103
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000001
RBP: ffff88813fead2e8 R08: dffffc0000000000 R09: ffffed1027fd5771
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88813feabb80
R13: ffffffff8cfcf300 R14: ffff88813feacdf8 R15: dffffc0000000000
schedule+0xb8/0x180 kernel/sched/core.c:6633
smpboot_thread_fn+0x604/0xa30 kernel/smpboot.c:160
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
</TASK>


---
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