[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <667a26bb-f414-0694-f0c6-299451fd8f2e@ti.com>
Date: Wed, 9 Jun 2021 20:04:24 +0300
From: Grygorii Strashko <grygorii.strashko@...com>
To: Toke Høiland-Jørgensen <toke@...hat.com>,
<bpf@...r.kernel.org>, <netdev@...r.kernel.org>
CC: Martin KaFai Lau <kafai@...com>,
Hangbin Liu <liuhangbin@...il.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Magnus Karlsson <magnus.karlsson@...il.com>,
"Paul E . McKenney" <paulmck@...nel.org>,
<linux-omap@...r.kernel.org>
Subject: Re: [PATCH bpf-next 17/17] net: ti: remove rcu_read_lock() around XDP
program invocation
On 09/06/2021 13:33, Toke Høiland-Jørgensen wrote:
> The cpsw driver has rcu_read_lock()/rcu_read_unlock() pairs around XDP
> program invocations. However, the actual lifetime of the objects referred
> by the XDP program invocation is longer, all the way through to the call to
> xdp_do_flush(), making the scope of the rcu_read_lock() too small. This
> turns out to be harmless because it all happens in a single NAPI poll
> cycle (and thus under local_bh_disable()), but it makes the rcu_read_lock()
> misleading.
>
> Rather than extend the scope of the rcu_read_lock(), just get rid of it
> entirely. With the addition of RCU annotations to the XDP_REDIRECT map
> types that take bh execution into account, lockdep even understands this to
> be safe, so there's really no reason to keep it around.
>
> Cc: Grygorii Strashko <grygorii.strashko@...com>
> Cc: linux-omap@...r.kernel.org
> Signed-off-by: Toke Høiland-Jørgensen <toke@...hat.com>
> ---
> drivers/net/ethernet/ti/cpsw_priv.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
Tested-by: Grygorii Strashko <grygorii.strashko@...com>
Reviewed-by: Grygorii Strashko <grygorii.strashko@...com>
--
Best regards,
grygorii
Powered by blists - more mailing lists