[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230109151336.GO4028633@paulmck-ThinkPad-P17-Gen-1>
Date: Mon, 9 Jan 2023 07:13:36 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: rcu@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...a.com, rostedt@...dmis.org,
Dave Chinner <david@...morbit.com>,
Dmitry Vyukov <dvyukov@...gle.com>
Subject: Re: [PATCH rcu 6/6] rcu: Allow up to five minutes expedited RCU CPU
stall-warning timeouts
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@...nel.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
Powered by blists - more mailing lists