[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aElLN5GD8FA2zya4@pc636>
Date: Wed, 11 Jun 2025 11:24:07 +0200
From: Uladzislau Rezki <urezki@...il.com>
To: Joel Fernandes <joelagnelf@...dia.com>
Cc: "Uladzislau Rezki (Sony)" <urezki@...il.com>,
"Paul E . McKenney" <paulmck@...nel.org>,
Joel Fernandes <joel@...lfernandes.org>,
Neeraj upadhyay <Neeraj.Upadhyay@....com>,
RCU <rcu@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
Frederic Weisbecker <frederic@...nel.org>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH 1/3] rcu: Return early if callback is not specified
On Tue, Jun 10, 2025 at 03:33:32PM -0400, Joel Fernandes wrote:
>
>
> On 6/10/2025 1:34 PM, Uladzislau Rezki (Sony) wrote:
> > Currently the call_rcu() API does not check whether a callback
> > pointer is NULL. If NULL is passed, rcu_core() will try to invoke
> > it, resulting in NULL pointer dereference and a kernel crash.
> >
> > To prevent this and improve debuggability, this patch adds a check
> > for NULL and emits a kernel stack trace to help identify a faulty
> > caller.
> >
> > Signed-off-by: Uladzislau Rezki (Sony) <urezki@...il.com>
>
> Reviewed-by: Joel Fernandes <joelagnelf@...dia.com>
>
> I will add this first one (only this one since we're discussing the others) to a
> new rcu/fixes-for-6.16 branch, but let me know if any objections.
>
> Will push that branch out during -rc2 or -rc3 after sufficient testing.
>
Yep, that sounds good to me about rc-2/3 releases.
--
Uladzislau Rezki
Powered by blists - more mailing lists