[v6.1] INFO: rcu detected stall in kauditd_thread (2)

0 views
Skip to first unread message

syzbot

unread,
Dec 11, 2023, 11:51:29 AM12/11/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e7cddbb41b63 Linux 6.1.67
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=162194fae80000
kernel config: https://syzkaller.appspot.com/x/.config?x=8160fc00d26f042b
dashboard link: https://syzkaller.appspot.com/bug?extid=4d37ebcdb19e4c39aac3
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/8956c6179c51/disk-e7cddbb4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d5ebbb26ed14/vmlinux-e7cddbb4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/30e370b152f6/bzImage-e7cddbb4.xz

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

rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
rcu: 0-...!: (1 GPs behind) idle=48ec/1/0x4000000000000000 softirq=85549/85550 fqs=4
(detected by 1, t=10504 jiffies, g=115389, q=193 ncpus=2)
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: kauditd Not tainted 6.1.67-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:hlock_class kernel/locking/lockdep.c:228 [inline]
RIP: 0010:__lock_acquire+0xf7f/0x1f80 kernel/locking/lockdep.c:5045
Code: 00 8b 1b 81 e3 ff 1f 00 00 48 89 d8 48 c1 e8 06 48 8d 3c c5 20 f2 48 90 be 08 00 00 00 e8 d9 8f 77 00 48 0f a3 1d f1 90 de 0e <0f> 83 bb 01 00 00 48 8d 04 5b 48 c1 e0 06 48 8d 98 20 51 18 90 48
RSP: 0018:ffffc90000007a60 EFLAGS: 00000057
RAX: 0000000000000001 RBX: 0000000000000004 RCX: ffffffff816a6127
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff9048f220
RBP: 944e01decf4df750 R08: dffffc0000000000 R09: fffffbfff2091e45
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880127a6418
R13: ffff8880127a5940 R14: 0000000000000001 R15: 1ffff110024f4c8d
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e722000 CR3: 0000000092fac000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<NMI>
</NMI>
<IRQ>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:350 [inline]
advance_sched+0x47/0x970 net/sched/sch_taprio.c:700
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x5e5/0xe50 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x392/0x980 kernel/time/hrtimer.c:1811
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:649
RIP: 0010:console_emit_next_record+0xc69/0xea0 kernel/printk/printk.c:2751
Code: 00 e8 eb 44 1c 00 44 0f b6 74 24 1f 4d 85 e4 75 07 e8 db 44 1c 00 eb 06 e8 d4 44 1c 00 fb 48 c7 84 24 a0 00 00 00 0e 36 e0 45 <42> c7 04 2b 00 00 00 00 4a c7 44 2b 0a 00 00 00 00 4a c7 44 2b 12
RSP: 0018:ffffc90000a3f760 EFLAGS: 00000293
RAX: ffffffff816e4d4c RBX: dffffc0000000000 RCX: ffff8880127a5940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000a3fa10 R08: ffffffff816e4d27 R09: fffffbfff2091e45
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000200
R13: 1ffff92000147f00 R14: 0000000000000001 R15: 0000000000000000
console_unlock+0x278/0x7c0 kernel/printk/printk.c:2871
vprintk_emit+0x523/0x740 kernel/printk/printk.c:2268
_printk+0xd1/0x111 kernel/printk/printk.c:2293
kauditd_printk_skb kernel/audit.c:536 [inline]
kauditd_hold_skb+0x1b8/0x200 kernel/audit.c:571
kauditd_send_queue+0x2a3/0x2f0 kernel/audit.c:756
kauditd_thread+0x758/0x990 kernel/audit.c:880
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: rcu_preempt kthread starved for 10485 jiffies! g115389 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:25752 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:1674
rcu_gp_kthread+0xa3/0x3a0 kernel/rcu/tree.c:1873
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
rcu: Stack dump where RCU GP kthread last ran:
CPU: 1 PID: 12358 Comm: syz-executor.3 Not tainted 6.1.67-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:csd_lock_wait kernel/smp.c:424 [inline]
RIP: 0010:smp_call_function_many_cond+0x1fb0/0x3460 kernel/smp.c:998
Code: 2f 44 89 ee 83 e6 01 31 ff 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
RSP: 0018:ffffc9000343f3a0 EFLAGS: 00000293
RAX: ffffffff817f52cb RBX: 1ffff1101730841d RCX: ffff888071e3d940
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc9000343f780 R08: ffffffff817f5294 R09: fffffbfff2091e4b
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000800000000
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff8880b98420e8
FS: 0000555555687480(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f048eac56be CR3: 0000000092fac000 CR4: 00000000003506e0
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
dup_mmap kernel/fork.c:712 [inline]
dup_mm kernel/fork.c:1540 [inline]
copy_mm+0x1357/0x1990 kernel/fork.c:1589
copy_process+0x19d5/0x4060 kernel/fork.c:2267
kernel_clone+0x222/0x920 kernel/fork.c:2682
__do_sys_clone kernel/fork.c:2823 [inline]
__se_sys_clone kernel/fork.c:2807 [inline]
__x64_sys_clone+0x231/0x280 kernel/fork.c:2807
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+0x63/0xcd
RIP: 0033:0x7f048de79bd3
Code: 1f 84 00 00 00 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffc98cb7b98 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f048de79bd3
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: 0000555555687750 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000001
</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