mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, rostedt@goodmis.org,
	Dave Chinner <david@fromorbit.com>,
	Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH rcu 6/6] rcu: Allow up to five minutes expedited RCU CPU stall-warning timeouts
Date: Mon, 9 Jan 2023 07:13:36 -0800	[thread overview]
Message-ID: <20230109151336.GO4028633@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <CAMuHMdU_+t=msiusxi3BxgFVxMO8Y-mMDoTLnx_RUzPXVWrdOQ@mail.gmail.com>

On Mon, Jan 09, 2023 at 11:10:10AM +0100, Geert Uytterhoeven wrote:
> Hi Paul,
> 
> Thanks for your patch, which is now commit 0d49d9123dcf41f7 ("rcu:
> Allow up to five minutes expedited RCU CPU stall-warning timeouts")
> in next-20230109.
> 
> On Thu, Jan 5, 2023 at 2:10 AM Paul E. McKenney <paulmck@kernel.org> wrote:
> > The maximum value of RCU CPU stall-warning timeouts has historically been
> > five minutes (300 seconds).  However, the recently introduced expedited
> > RCU CPU stall-warning timeout is instead limited to 21 seconds.  This
> > causes problems for CI/fuzzing services such as syzkaller by obscuring
> > the issue in question with expedited RCU CPU stall-warning timeout splats.
> >
> > This commit therefore sets the RCU_EXP_CPU_STALL_TIMEOUT Kconfig options
> > upper bound to 300000 milliseconds, which is 300 seconds and 5 minutes.
> 
> s/and/or/

Good eyes!  I will apply with attribution on my next rebase.

							Thanx, Paul

      reply	other threads:[~2023-01-09 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  0:51 [PATCH rcu 0/6] RCU CPU stall-warning updates for v6.3 Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 1/6] genirq: Fix the return type of kstat_cpu_irqs_sum() Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 2/6] sched: Add helper kstat_cpu_softirqs_sum() Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 3/6] sched: Add helper nr_context_switches_cpu() Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 4/6] rcu: Add RCU stall diagnosis information Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 5/6] rcu: Align the output of RCU CPU stall warning messages Paul E. McKenney
2023-01-05  0:51 ` [PATCH rcu 6/6] rcu: Allow up to five minutes expedited RCU CPU stall-warning timeouts Paul E. McKenney
2023-01-09 10:10   ` Geert Uytterhoeven
2023-01-09 15:13     ` Paul E. McKenney [this message]

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=20230109151336.GO4028633@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=david@fromorbit.com \
    --cc=dvyukov@google.com \
    --cc=geert@linux-m68k.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rcu@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®