Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230105005105.GA1772125@paulmck-ThinkPad-P17-Gen-1> <20230105005126.1772294-6-paulmck@kernel.org>
In-Reply-To: <20230105005126.1772294-6-paulmck@kernel.org>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Mon, 9 Jan 2023 11:10:10 +0100
Message-ID: <CAMuHMdU_+t=msiusxi3BxgFVxMO8Y-mMDoTLnx_RUzPXVWrdOQ@mail.gmail.com>
Subject: Re: [PATCH rcu 6/6] rcu: Allow up to five minutes expedited RCU CPU
 stall-warning timeouts
To:     "Paul E. McKenney" <paulmck@kernel.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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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/

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-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