All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Eric Dumazet <edumazet@google.com>,
	Paul Moore <paul@paul-moore.com>,
	syzbot <syzbot+81f5ca46b043d4a1b789@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [audit?] [bpf?] INFO: rcu detected stall in kauditd_thread (4)
Date: Sun, 31 Mar 2024 15:25:02 +0800	[thread overview]
Message-ID: <20240331072502.3456-1-hdanton@sina.com> (raw)
In-Reply-To: <ZgVvN5DmLLMaAg_S@alley>

On Thu, 28 Mar 2024 15:44:27 +0100 Petr Mladek <pmladek@suse.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/

  reply	other threads:[~2024-03-31  7:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 18:39 [syzbot] [audit?] [bpf?] INFO: rcu detected stall in kauditd_thread (4) syzbot
2024-03-27 19:16 ` Paul Moore
2024-03-28 14:44   ` Petr Mladek
2024-03-31  7:25     ` Hillf Danton [this message]
2024-03-28 23:27 ` Hillf Danton
2024-03-29 17:08   ` syzbot
2024-03-30  0:44 ` Hillf Danton
2024-03-30 15:46   ` syzbot
2024-03-31  0:09 ` Hillf Danton
2024-03-31  0:09   ` Hillf Danton
2024-03-31  6:39   ` syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240331072502.3456-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=pmladek@suse.com \
    --cc=syzbot+81f5ca46b043d4a1b789@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.