From: Jakub Kicinski <kuba@kernel.org>
To: Binbin Deng <18983559317@163.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v1] net: sit: unlink PRL list before RCU free
Date: Tue, 20 Oct 2026 13:55:43 -0700 [thread overview]
Message-ID: <20261020135543.4e44549f@kernel.org> (raw)
In-Reply-To: <20261014060803.286885-1-18983559317@163.com>
On Wed, 14 Oct 2026 14:08:03 +0800 Binbin Deng wrote:
> Deleting all PRL entries queues the old list for RCU freeing before
> t->prl is cleared. A reader that enters an RCU critical section after
> call_rcu() but before the pointer is cleared can still fetch the old
> list, and that critical section is not guaranteed to be covered by the
> grace period associated with the callback. RTNL does not prevent this
> race: RCU readers do not acquire it and the writer remains preemptible.
> It can lead to use-after-free.
Eric already fixed this
prev parent reply other threads:[~2026-10-20 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 6:08 Binbin Deng
2026-10-14 6:15 ` netdev-bot+sinfo
2026-10-20 20:55 ` Jakub Kicinski [this message]
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=20261020135543.4e44549f@kernel.org \
--to=kuba@kernel.org \
--cc=18983559317@163.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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®