From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] netfilter: xt_owner: no longer acquire sk_callback_lock in mt_owner()
Date: Tue, 24 Feb 2026 13:52:19 +0100 [thread overview]
Message-ID: <aZ2fA2x5nHsnQoBu@strlen.de> (raw)
In-Reply-To: <20260224122856.3152608-1-edumazet@google.com>
Eric Dumazet <edumazet@google.com> wrote:
> After commit 983512f3a87f ("net: Drop the lock in skb_may_tx_timestamp()")
> from Sebastian Andrzej Siewior, apply the same logic in mt_owner()
> to avoid touching sk_callback_lock.
> - read_lock_bh(&sk->sk_callback_lock);
> - filp = sk->sk_socket ? sk->sk_socket->file : NULL;
> + /* The sk pointer remains valid as long as the skb is. The sk_socket and
> + * file pointer may become NULL if the socket is closed. Both structures
> + * (including file->cred) are RCU freed which means they can be accessed
> + * within a RCU read section.
> + */
> + rcu_read_lock();
> + sock = READ_ONCE(sk->sk_socket);
> + filp = sock ? READ_ONCE(sock->file) : NULL;
Thanks for doing this Eric!
Minor nit: rcu_read_lock is already acquired from nf_hook() helper, so
we aleays have it in both iptables and nftables.
Reviewed-by: Florian Westphal <fw@strlen.de>
next prev parent reply other threads:[~2026-02-24 12:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 12:28 [PATCH net-next] netfilter: xt_owner: no longer acquire sk_callback_lock in mt_owner() Eric Dumazet
2026-02-24 12:52 ` Florian Westphal [this message]
2026-02-24 15:40 ` Eric Dumazet
2026-02-24 15:49 ` Florian Westphal
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=aZ2fA2x5nHsnQoBu@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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