From: Jakub Kicinski <kuba@kernel.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Breno Leitao <leitao@debian.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Waiman Long <longman@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Hayes Wang <hayeswang@realtek.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: Assert proper context while calling napi_schedule()
Date: Fri, 14 Feb 2025 14:00:45 -0800 [thread overview]
Message-ID: <20250214140045.547f1396@kernel.org> (raw)
In-Reply-To: <Z65YNFGxh-ORF7hm@pavilion.home>
On Thu, 13 Feb 2025 21:38:12 +0100 Frederic Weisbecker wrote:
> > > Just to make sure I follow the netpoll issue. What would you like to fix
> > > in netpoll exactly?
> >
> > Nothing in netpoll, the problem is that netdevsim calls napi_schedule
> > from the xmit path. That's incompatible with netpoll. We should fix
> > netdevsim instead (unless more real drivers need napi-from-xmit to
> > work).
>
> Let me clarify, because I don't know much this area. If the problem is that xmit
> can't call napi_schedule() by design, then I defer to you. But if the problem is that
> napi_schedule() may or may not be called from an interrupt, please note that
> local_bh_enable() won't run softirqs from a hardirq and will instead defer to
> IRQ tail. So it's fine to do an unconditional pair of local_bh_disable() / local_bh_enable().
I don't know where this is in the code TBH, but my understanding is
that HW IRQs - yes, as you say it'd be safe; the problem is that
we have local_irq_save() all over the place. And that is neither
protected from local_bh_enable(), not does irq_restore execute softirqs.
next prev parent reply other threads:[~2025-02-14 22:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 17:43 [PATCH 0/2] net: Fix/prevent napi_schedule() call from bare task context Frederic Weisbecker
2025-02-12 17:43 ` [PATCH 1/2] net: Assert proper context while calling napi_schedule() Frederic Weisbecker
2025-02-13 3:48 ` Jakub Kicinski
2025-02-13 9:58 ` Breno Leitao
2025-02-13 15:14 ` Jakub Kicinski
2025-02-13 18:14 ` Breno Leitao
2025-02-13 19:04 ` Jakub Kicinski
2025-02-13 20:38 ` Frederic Weisbecker
2025-02-14 22:00 ` Jakub Kicinski [this message]
2025-02-15 21:16 ` Frederic Weisbecker
2025-02-14 13:05 ` Breno Leitao
2025-02-14 16:43 ` Breno Leitao
2025-02-14 22:10 ` Jakub Kicinski
2025-02-17 16:46 ` Breno Leitao
2025-02-17 17:37 ` Jakub Kicinski
2025-02-13 20:39 ` Frederic Weisbecker
2025-02-14 22:03 ` Jakub Kicinski
2025-02-12 17:43 ` [PATCH 2/2] r8152: Call napi_schedule() from proper context Frederic Weisbecker
2025-02-12 20:49 ` Francois Romieu
2025-02-12 20:58 ` Frederic Weisbecker
2025-02-18 20:12 ` Paul Menzel
2025-04-27 20:50 ` Tobias Jakobi
2025-04-28 17:49 ` Jakub Kicinski
2025-04-28 20:26 ` Tobias Jakobi
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=20250214140045.547f1396@kernel.org \
--to=kuba@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frederic@kernel.org \
--cc=hayeswang@realtek.com \
--cc=horms@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).