From: Joel Fernandes <joel@joelfernandes.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: paulmck@kernel.org, netdev@vger.kernel.org, frederic@kernel.org,
neeraj.upadhyay@kernel.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org, kees@kernel.org,
matttbe@kernel.org
Subject: Re: [PATCH rcu] configs/debug: make sure PROVE_RCU_LIST=y takes effect
Date: Tue, 15 Oct 2024 22:23:58 -0400 [thread overview]
Message-ID: <670f23c3.050a0220.1fe46c.5dd2@mx.google.com> (raw)
In-Reply-To: <20241016011144.3058445-1-kuba@kernel.org>
On Tue, Oct 15, 2024 at 06:11:44PM -0700, Jakub Kicinski wrote:
> Commit 0aaa8977acbf ("configs: introduce debug.config for CI-like setup")
> added CONFIG_PROVE_RCU_LIST=y to the common CI config,
> but RCU_EXPERT is not set, and it's a dependency for
> CONFIG_PROVE_RCU_LIST=y. Make sure CIs take advantage
> of CONFIG_PROVE_RCU_LIST=y, recent fixes in networking
> indicate that it does catch bugs.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
thanks,
- Joel
> ---
> I'd be slightly tempted to still send it to Linux for v6.12.
>
> CC: paulmck@kernel.org
> CC: frederic@kernel.org
> CC: neeraj.upadhyay@kernel.org
> CC: joel@joelfernandes.org
> CC: rcu@vger.kernel.org
> CC: linux-kernel@vger.kernel.org
> CC: kees@kernel.org
> CC: matttbe@kernel.org
> ---
> kernel/configs/debug.config | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/configs/debug.config b/kernel/configs/debug.config
> index 509ee703de15..20552f163930 100644
> --- a/kernel/configs/debug.config
> +++ b/kernel/configs/debug.config
> @@ -103,6 +103,7 @@ CONFIG_BUG_ON_DATA_CORRUPTION=y
> #
> # RCU Debugging
> #
> +CONFIG_RCU_EXPERT=y
> CONFIG_PROVE_RCU=y
> CONFIG_PROVE_RCU_LIST=y
> #
> --
> 2.46.2
>
next prev parent reply other threads:[~2024-10-16 2:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 1:11 [PATCH rcu] configs/debug: make sure PROVE_RCU_LIST=y takes effect Jakub Kicinski
2024-10-16 2:23 ` Joel Fernandes [this message]
2024-10-16 15:18 ` Matthieu Baerts
2024-10-16 15:29 ` Matthieu Baerts
2024-10-28 17:22 ` Jakub Kicinski
2024-10-28 18:04 ` Matthieu Baerts
2024-10-16 15:50 ` Paul E. McKenney
2024-10-17 15:36 ` Simon Horman
2024-10-28 20:00 ` patchwork-bot+netdevbpf
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=670f23c3.050a0220.1fe46c.5dd2@mx.google.com \
--to=joel@joelfernandes.org \
--cc=frederic@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.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 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.