[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240331072502.3456-1-hdanton@sina.com>
Date: Sun, 31 Mar 2024 15:25:02 +0800
From: Hillf Danton <hdanton@...a.com>
To: Petr Mladek <pmladek@...e.com>
Cc: Eric Dumazet <edumazet@...gle.com>,
Paul Moore <paul@...l-moore.com>,
syzbot <syzbot+81f5ca46b043d4a1b789@...kaller.appspotmail.com>,
linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [audit?] [bpf?] INFO: rcu detected stall in kauditd_thread (4)
On Thu, 28 Mar 2024 15:44:27 +0100 Petr Mladek <pmladek@...e.com>
> > > Call Trace:
> > > <IRQ>
> > > </IRQ>
> > > <TASK>
> > > csd_lock_wait kernel/smp.c:311 [inline]
> > > smp_call_function_many_cond+0x50b/0x1590 kernel/smp.c:855
> > > on_each_cpu_cond_mask+0x40/0x90 kernel/smp.c:1023
> > > on_each_cpu include/linux/smp.h:71 [inline]
>
> It seems that this is really stuck because it is not able to
> run something on the other CPU.
>
> IMHO, the primary problem is in the code proceed by the hrtimer.
> Adding networking people into Cc.
Yes the taprio hrtimer is a CPU hog [1]
[1] https://lore.kernel.org/lkml/00000000000003c53d0614ef21a4@google.com/
Powered by blists - more mailing lists