[v6.1] INFO: rcu detected stall in mod_objcg_state
1 view
Skip to first unread message
syzbot
Mar 9, 2024, 4:03:25 AMMar 9
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 61adba85cc40 Linux 6.1.81
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12feada6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=41dc7343796eb054
dashboard link: https://syzkaller.appspot.com/bug?extid=b3dcae6d3c20133d6ab9
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/bce1b8db2435/disk-61adba85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/488c5d1c7e73/vmlinux-61adba85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0821e919f99/bzImage-61adba85.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b3dcae...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (1 GPs behind) idle=763c/1/0x4000000000000000 softirq=50068/50069 fqs=486
(detected by 1, t=10503 jiffies, g=66809, q=1028 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.81-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:__sanitizer_cov_trace_pc+0x58/0x60 kernel/kcov.c:225
Code: f8 15 00 00 83 fa 02 75 21 48 8b 91 00 16 00 00 48 8b 32 48 8d 7e 01 8b 89 fc 15 00 00 48 39 cf 73 08 48 89 3a 48 89 44 f2 08 <c3> 0f 1f 80 00 00 00 00 4c 8b 04 24 65 48 8b 15 c4 ef 77 7e 65 8b
RSP: 0018:ffffc90000007cb8 EFLAGS: 00000046
RAX: ffffffff88b3b121 RBX: 0000000000000001 RCX: ffff88813feabb80
RDX: 0000000080010101 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff888016eb22e8 R08: ffffffff88b3b114 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff888016eb2000
R13: ffff888016eb2340 R14: dffffc0000000000 R15: ffff88813feac648
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1f72b02463 CR3: 000000003511b000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
advance_sched+0x81/0x970 net/sched/sch_taprio.c:701
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:mod_objcg_state+0x5d4/0x920 mm/memcontrol.c:3215
Code: 3c 23 00 74 08 4c 89 f7 e8 89 fd f8 ff f6 84 24 81 00 00 00 02 0f 85 85 00 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 8b 7c 24 28 <48> 85 ff 74 05 e8 72 ad 00 00 48 c7 44 24 60 0e 36 e0 45 48 8b 44
RSP: 0018:ffffc900001478e0 EFLAGS: 00000206
RAX: 7a2e3d6c0292dc00 RBX: 1ffff92000028f2c RCX: ffffffff91c8d103
RDX: dffffc0000000000 RSI: ffffffff8aebed40 RDI: 0000000000000000
RBP: ffffc900001479f0 R08: dffffc0000000000 R09: fffffbfff1ce6bf6
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000054 R14: ffffc90000147960 R15: 0000000000000246
memcg_slab_free_hook mm/slab.h:570 [inline]
slab_free mm/slub.c:3656 [inline]
kmem_cache_free+0x188/0x510 mm/slub.c:3683
rcu_do_batch kernel/rcu/tree.c:2296 [inline]
rcu_core+0xad4/0x17e0 kernel/rcu/tree.c:2556
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x52c/0xa30 kernel/smpboot.c:164
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
rcu: rcu_preempt kthread starved for 8020 jiffies! g66809 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
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:26648 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
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2d2/0x1120 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 1 PID: 3586 Comm: syz-executor.1 Not tainted 6.1.81-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:csd_lock_wait kernel/smp.c:424 [inline]
RIP: 0010:smp_call_function_many_cond+0x1fb9/0x3460 kernel/smp.c:998
Code: e8 ec 42 0b 00 41 83 e5 01 49 bd 00 00 00 00 00 fc ff df 75 0a e8 77 3f 0b 00 e9 1b ff ff ff f3 90 42 0f b6 04 2b 84 c0 75 14 <41> f7 07 01 00 00 00 0f 84 fe fe ff ff e8 55 3f 0b 00 eb e1 44 89
RSP: 0018:ffffc900048ef100 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff1101730859d RCX: ffff888015788000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900048ef4e0 R08: ffffffff817f3f84 R09: fffff5200091de11
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880b9842ce8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffd5574e50 CR3: 000000007dea8000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1166
__flush_tlb_multi arch/x86/include/asm/paravirt.h:87 [inline]
flush_tlb_multi arch/x86/mm/tlb.c:924 [inline]
flush_tlb_mm_range+0x353/0x590 arch/x86/mm/tlb.c:1010
tlb_flush arch/x86/include/asm/tlb.h:20 [inline]
tlb_flush_mmu_tlbonly+0x1ab/0x410 include/asm-generic/tlb.h:430
tlb_flush_mmu+0x28/0x210 mm/mmu_gather.c:260
tlb_finish_mmu+0xce/0x1f0 mm/mmu_gather.c:361
exit_mmap+0x3c3/0x9f0 mm/mmap.c:3239
__mmput+0x115/0x3c0 kernel/fork.c:1199
exit_mm+0x226/0x300 kernel/exit.c:563
do_exit+0x9f6/0x26a0 kernel/exit.c:856
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
get_signal+0x16f7/0x17d0 kernel/signal.c:2862
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f14952a91b5
Code: Unable to access opcode bytes at 0x7f14952a918b.
RSP: 002b:00007fff2b14dbb0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e6
RAX: fffffffffffffdfc RBX: 00000000000009a1 RCX: 00007f14952a91b5
RDX: 00007fff2b14dbf0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fff2b14dc7c R08: 0000000000000000 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 00000000001289eb R14: 0000000000128956 R15: 0000000000000009
</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
syzbot found the following issue on:
HEAD commit: 61adba85cc40 Linux 6.1.81
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12feada6180000
kernel config: https://syzkaller.appspot.com/x/.config?x=41dc7343796eb054
dashboard link: https://syzkaller.appspot.com/bug?extid=b3dcae6d3c20133d6ab9
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/bce1b8db2435/disk-61adba85.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/488c5d1c7e73/vmlinux-61adba85.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b0821e919f99/bzImage-61adba85.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b3dcae...@syzkaller.appspotmail.com
rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (1 GPs behind) idle=763c/1/0x4000000000000000 softirq=50068/50069 fqs=486
(detected by 1, t=10503 jiffies, g=66809, q=1028 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted 6.1.81-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:__sanitizer_cov_trace_pc+0x58/0x60 kernel/kcov.c:225
Code: f8 15 00 00 83 fa 02 75 21 48 8b 91 00 16 00 00 48 8b 32 48 8d 7e 01 8b 89 fc 15 00 00 48 39 cf 73 08 48 89 3a 48 89 44 f2 08 <c3> 0f 1f 80 00 00 00 00 4c 8b 04 24 65 48 8b 15 c4 ef 77 7e 65 8b
RSP: 0018:ffffc90000007cb8 EFLAGS: 00000046
RAX: ffffffff88b3b121 RBX: 0000000000000001 RCX: ffff88813feabb80
RDX: 0000000080010101 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff888016eb22e8 R08: ffffffff88b3b114 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: ffff888016eb2000
R13: ffff888016eb2340 R14: dffffc0000000000 R15: ffff88813feac648
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1f72b02463 CR3: 000000003511b000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
advance_sched+0x81/0x970 net/sched/sch_taprio.c:701
__run_hrtimer kernel/time/hrtimer.c:1686 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1750
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1812
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x156/0x580 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x8c/0xb0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:653
RIP: 0010:mod_objcg_state+0x5d4/0x920 mm/memcontrol.c:3215
Code: 3c 23 00 74 08 4c 89 f7 e8 89 fd f8 ff f6 84 24 81 00 00 00 02 0f 85 85 00 00 00 41 f7 c7 00 02 00 00 74 01 fb 48 8b 7c 24 28 <48> 85 ff 74 05 e8 72 ad 00 00 48 c7 44 24 60 0e 36 e0 45 48 8b 44
RSP: 0018:ffffc900001478e0 EFLAGS: 00000206
RAX: 7a2e3d6c0292dc00 RBX: 1ffff92000028f2c RCX: ffffffff91c8d103
RDX: dffffc0000000000 RSI: ffffffff8aebed40 RDI: 0000000000000000
RBP: ffffc900001479f0 R08: dffffc0000000000 R09: fffffbfff1ce6bf6
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000054 R14: ffffc90000147960 R15: 0000000000000246
memcg_slab_free_hook mm/slab.h:570 [inline]
slab_free mm/slub.c:3656 [inline]
kmem_cache_free+0x188/0x510 mm/slub.c:3683
rcu_do_batch kernel/rcu/tree.c:2296 [inline]
rcu_core+0xad4/0x17e0 kernel/rcu/tree.c:2556
__do_softirq+0x2e9/0xa4c kernel/softirq.c:571
run_ksoftirqd+0xc1/0x120 kernel/softirq.c:934
smpboot_thread_fn+0x52c/0xa30 kernel/smpboot.c:164
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
rcu: rcu_preempt kthread starved for 8020 jiffies! g66809 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=1
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:26648 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
schedule+0xbf/0x180 kernel/sched/core.c:6634
schedule_timeout+0x1b9/0x300 kernel/time/timer.c:1935
rcu_gp_fqs_loop+0x2d2/0x1120 kernel/rcu/tree.c:1706
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1905
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:307
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 1 PID: 3586 Comm: syz-executor.1 Not tainted 6.1.81-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
RIP: 0010:csd_lock_wait kernel/smp.c:424 [inline]
RIP: 0010:smp_call_function_many_cond+0x1fb9/0x3460 kernel/smp.c:998
Code: e8 ec 42 0b 00 41 83 e5 01 49 bd 00 00 00 00 00 fc ff df 75 0a e8 77 3f 0b 00 e9 1b ff ff ff f3 90 42 0f b6 04 2b 84 c0 75 14 <41> f7 07 01 00 00 00 0f 84 fe fe ff ff e8 55 3f 0b 00 eb e1 44 89
RSP: 0018:ffffc900048ef100 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 1ffff1101730859d RCX: ffff888015788000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc900048ef4e0 R08: ffffffff817f3f84 R09: fffff5200091de11
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880b9842ce8
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffd5574e50 CR3: 000000007dea8000 CR4: 00000000003526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
</IRQ>
<TASK>
on_each_cpu_cond_mask+0x3b/0x80 kernel/smp.c:1166
__flush_tlb_multi arch/x86/include/asm/paravirt.h:87 [inline]
flush_tlb_multi arch/x86/mm/tlb.c:924 [inline]
flush_tlb_mm_range+0x353/0x590 arch/x86/mm/tlb.c:1010
tlb_flush arch/x86/include/asm/tlb.h:20 [inline]
tlb_flush_mmu_tlbonly+0x1ab/0x410 include/asm-generic/tlb.h:430
tlb_flush_mmu+0x28/0x210 mm/mmu_gather.c:260
tlb_finish_mmu+0xce/0x1f0 mm/mmu_gather.c:361
exit_mmap+0x3c3/0x9f0 mm/mmap.c:3239
__mmput+0x115/0x3c0 kernel/fork.c:1199
exit_mm+0x226/0x300 kernel/exit.c:563
do_exit+0x9f6/0x26a0 kernel/exit.c:856
do_group_exit+0x202/0x2b0 kernel/exit.c:1019
get_signal+0x16f7/0x17d0 kernel/signal.c:2862
arch_do_signal_or_restart+0xb0/0x1a10 arch/x86/kernel/signal.c:871
exit_to_user_mode_loop+0x6a/0x100 kernel/entry/common.c:168
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x60/0x270 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f14952a91b5
Code: Unable to access opcode bytes at 0x7f14952a918b.
RSP: 002b:00007fff2b14dbb0 EFLAGS: 00000293 ORIG_RAX: 00000000000000e6
RAX: fffffffffffffdfc RBX: 00000000000009a1 RCX: 00007f14952a91b5
RDX: 00007fff2b14dbf0 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00007fff2b14dc7c R08: 0000000000000000 R09: 0000000000000010
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000032
R13: 00000000001289eb R14: 0000000000128956 R15: 0000000000000009
</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