[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iLXLZGvuDhmTJV19A4jBpYGaAYp3hh3kjDUaDDZJqDLKw@mail.gmail.com>
Date: Tue, 29 Jul 2025 09:14:06 -0700
From: Eric Dumazet <edumazet@...gle.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: Sharath Chandra Vurukala <quic_sharathv@...cinc.com>, davem@...emloft.net, dsahern@...nel.org,
kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
quic_kapandey@...cinc.com, quic_subashab@...cinc.com
Subject: Re: [PATCH v2] net: Add locking to protect skb->dev access in ip_output
On Tue, Jul 29, 2025 at 9:11 AM Willem de Bruijn
<willemdebruijn.kernel@...il.com> wrote:
>
> Sharath Chandra Vurukala wrote:
>
> > >> + rcu_read_lock();
>
> How do we know that all paths taken from here are safe to be run
> inside an rcu readside critical section btw?
This is totally safe ;)
Powered by blists - more mailing lists