From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zqiang <qiang1.zhang@intel.com>
Cc: frederic@kernel.org, quic_neeraju@quicinc.com,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rcu: Make tiny RCU support leak callbacks for debug-object errors
Date: Tue, 5 Jul 2022 10:41:09 -0700 [thread overview]
Message-ID: <20220705174109.GD1790663@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220701024404.2228367-1-qiang1.zhang@intel.com>
On Fri, Jul 01, 2022 at 10:44:04AM +0800, Zqiang wrote:
> Currently, only tree RCU support leak callbacks setting when do
> duplicate call_rcu(). this commit add leak callbacks setting when
> fo duplicate call_rcu() for tiny RCU.
>
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>
This does look plausible, thank you!
What testing have you done?
One important test for Tiny RCU is that the size of the kernel not
grow without a very good reason. In this case, the added code should
be dead code in a production build (CONFIG_DEBUG_OBJECTS_RCU_HEAD=n),
but it is good to check.
It is of course also good to check that the messages print as expected,
which is what rcutorture.object_debug is there to help with.
Thanx, Paul
> ---
> v1->v2:
> for do duplicate kvfree_call_rcu(), not set leak callbacks.
>
> kernel/rcu/tiny.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/tiny.c b/kernel/rcu/tiny.c
> index f0561ee16b9c..943d431b908f 100644
> --- a/kernel/rcu/tiny.c
> +++ b/kernel/rcu/tiny.c
> @@ -158,6 +158,10 @@ void synchronize_rcu(void)
> }
> EXPORT_SYMBOL_GPL(synchronize_rcu);
>
> +static void tiny_rcu_leak_callback(struct rcu_head *rhp)
> +{
> +}
> +
> /*
> * Post an RCU callback to be invoked after the end of an RCU grace
> * period. But since we have but one CPU, that would be after any
> @@ -165,9 +169,20 @@ EXPORT_SYMBOL_GPL(synchronize_rcu);
> */
> void call_rcu(struct rcu_head *head, rcu_callback_t func)
> {
> + static atomic_t doublefrees;
> unsigned long flags;
>
> - debug_rcu_head_queue(head);
> + if (debug_rcu_head_queue(head)) {
> + if (atomic_inc_return(&doublefrees) < 4) {
> + pr_err("%s(): Double-freed CB %p->%pS()!!! ", __func__, head, head->func);
> + mem_dump_obj(head);
> + }
> +
> + if (!__is_kvfree_rcu_offset((unsigned long)head->func))
> + WRITE_ONCE(head->func, tiny_rcu_leak_callback);
> + return;
> + }
> +
> head->func = func;
> head->next = NULL;
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-07-05 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 2:44 Zqiang
2022-07-05 17:41 ` Paul E. McKenney [this message]
2022-07-06 2:00 ` Zhang, Qiang1
2022-07-06 3:50 ` Paul E. McKenney
2022-07-06 4:09 ` Zhang, Qiang1
2022-07-06 4:24 ` Zhang, Qiang1
2022-07-08 22:13 ` Paul E. McKenney
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=20220705174109.GD1790663@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=quic_neeraju@quicinc.com \
--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 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®