From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Runyu Xiao <runyu.xiao@seu.edu.cn>, davem <davem@davemloft.net>,
edumazet <edumazet@google.com>, pabeni <pabeni@redhat.com>,
horms <horms@kernel.org>, sashal <sashal@kernel.org>,
bigeasy <bigeasy@linutronix.de>, netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"jianhao.xu" <jianhao.xu@seu.edu.cn>
Subject: Re: [RFC PATCH net-next] netpoll: hold RCU while walking napi_list
Date: Mon, 29 Jun 2026 15:58:33 -0700 [thread overview]
Message-ID: <20260629155833.1b1c2c26@kernel.org> (raw)
In-Reply-To: <akJSi1g0F2k9a3cs@gmail.com>
On Mon, 29 Jun 2026 04:17:10 -0700 Breno Leitao wrote:
> > Sure, sorry for not including it in the RFC. The warning was from the
> > reviewed reproducer used for the CONFIG_PROVE_RCU_LIST triage, not from
> > a production crash. The relevant part of the dmesg is:
>
> Reading it, it does not come from the kernel's netpoll code at
> all -- it comes from an out-of-tree module (!?)
Yes, like Breno says, we need an in-kernel path that can trigger the
issue. Out-of-tree reproducers can be useful to validate the fix, but
they are not useful to prove that a problem actually exists.
We try to avoid defensive programming in the kernel.
next prev parent reply other threads:[~2026-06-29 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 10:12 [RFC PATCH net-next] netpoll: hold RCU while walking napi_list Runyu Xiao
2026-06-27 21:21 ` Jakub Kicinski
2026-06-28 5:04 ` Runyu Xiao
2026-06-29 11:17 ` Breno Leitao
2026-06-29 22:58 ` Jakub Kicinski [this message]
2026-07-03 3:17 ` Runyu Xiao
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=20260629155833.1b1c2c26@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=runyu.xiao@seu.edu.cn \
--cc=sashal@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.