[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdU_+t=msiusxi3BxgFVxMO8Y-mMDoTLnx_RUzPXVWrdOQ@mail.gmail.com>
Date: Mon, 9 Jan 2023 11:10:10 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: "Paul E. McKenney" <paulmck@...nel.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
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/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists