Netdev List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
	netdev@vger.kernel.org,  "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	 Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	 Stephen Hemminger <stephen@networkplumber.org>,
	Arend van Spriel <arend.vanspriel@broadcom.com>,
	 linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net v2 1/2] netpoll: use a raw lock for the deferred transmit queue
Date: Fri, 13 Nov 2026 07:21:06 -0800	[thread overview]
Message-ID: <avcqBLwy_TB0w6PF@gmail.com> (raw)
In-Reply-To: <20261009155225.6Uy7b0wd@linutronix.de>

Hello Sebastian,

On Fri, Oct 09, 2026 at 05:52:25PM +0200, Sebastian Andrzej Siewior wrote:
> I would suggest to untangle that local-irq-disable assumption. Then we
> end up with the ::write_atomic callback on PREEMPT_RT which will raise
> warnings. But those will appear only on panic() and as the last console
> due to CON_NBCON_ATOMIC_UNSAFE so everything will go according to the
> plan.
> On !RT the whole __netpoll_send_skb() will be with disabled interrupts
> due to the console lock. On RT it won't and I don't know if anything
> down the call chain assumes that.

Thanks for the patch, On PREEMPT_RT, the send path is clean.
all the selftest I have are passing fine, without a single splat, while
the unpatched kernel produces about a dozen over the same tests. 

On !RT, the first message triggers, but it doesn't seem a big deal.

  WARNING: kernel/softirq.c:453 at __local_bh_enable_ip+0x118/0x120, CPU#4: pr/netcons_netc/307
  ...
  Call trace:
   __local_bh_enable_ip+0x118/0x120 (P)
   netpoll_send_skb+0x1a8/0x364
   send_udp+0x348/0x4a8
   netconsole_write+0x16c/0x628
   nbcon_emit_next_record+0x150/0x3cc
   nbcon_emit_one+0x74/0x158
   nbcon_kthread_func+0x18c/0x258
   kthread+0x108/0x134

Anyway, is this patch something you are planning to send officially?

Thanks,
--breno

  parent reply	other threads:[~2026-11-13 15:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  6:42 [PATCH net 0/2] netpoll: fix PREEMPT_RT deferred transmit locking Karl Mehltretter
2026-09-28  6:42 ` [PATCH net 1/2] netpoll: use a raw lock for the deferred transmit queue Karl Mehltretter
2026-09-30 21:43   ` netdev-bot+sashiko
2026-09-28  6:42 ` [PATCH net 2/2] netpoll: avoid blocking on the transmit lock in queue_process Karl Mehltretter
     [not found]   ` <20260929064307.569CE1F000FF@smtp.kernel.org>
2026-09-30 18:38     ` Karl Mehltretter
2026-09-30 21:43   ` netdev-bot+sashiko
2026-09-30 19:21 ` [PATCH net v2 0/2] netpoll: fix PREEMPT_RT deferred transmit locking Karl Mehltretter
2026-09-30 19:21 ` [PATCH net v2 1/2] netpoll: use a raw lock for the deferred transmit queue Karl Mehltretter
2026-10-01  7:48   ` Sebastian Andrzej Siewior
2026-10-01 23:30     ` Karl Mehltretter
2026-10-09 15:52       ` Sebastian Andrzej Siewior
2026-10-11 19:10         ` Karl Mehltretter
2026-11-13 15:21         ` Breno Leitao [this message]
2026-10-01 23:43   ` Jakub Kicinski
2026-10-02  0:17     ` Karl Mehltretter
2026-09-30 19:21 ` [PATCH net v2 2/2] netpoll: avoid blocking on the transmit lock in queue_process Karl Mehltretter

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=avcqBLwy_TB0w6PF@gmail.com \
    --to=leitao@debian.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kmehltretter@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=stephen@networkplumber.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