From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, wander@redhat.com, rostedt@goodmis.org,
clrkwllms@kernel.org, jgarzik@redhat.com, yuma@redhat.com,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net 0/4][pull request] igb: fix igb_msix_other() handling for PREEMPT_RT
Date: Wed, 5 Feb 2025 10:48:18 +0100 [thread overview]
Message-ID: <20250205094818.I-Jl44AK@linutronix.de> (raw)
In-Reply-To: <20250204175243.810189-1-anthony.l.nguyen@intel.com>
On 2025-02-04 09:52:36 [-0800], Tony Nguyen wrote:
> Wander Lairson Costa says:
>
> This is the second attempt at fixing the behavior of igb_msix_other()
> for PREEMPT_RT. The previous attempt [1] was reverted [2] following
> concerns raised by Sebastian [3].
I still prefer a solution where we don't have the ifdef in the driver. I
was presented two traces but I didn't get why it works in once case but
not in the other. Maybe it was too obvious.
In the mean time:
igb_msg_task_irq_safe()
-> vfs_raw_spin_lock_irqsave() // raw_spinlock_t
-> igb_vf_reset_event()
-> igb_vf_reset()
-> igb_set_rx_mode()
-> igb_write_mc_addr_list()
-> mta_list = kcalloc(netdev_mc_count(netdev), 6, GFP_ATOMIC); // kaboom?
By explicitly disabling preemption or using a raw_spinlock_t you need to
pay attention not to do anything that might lead to unbounded loops
(like iterating over many lists, polling on a bit for ages, …) and
paying attention that the whole API underneath that it is not doing that
is allowed to.
Sebastian
next prev parent reply other threads:[~2025-02-05 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 17:52 [PATCH net 0/4][pull request] igb: fix igb_msix_other() handling for PREEMPT_RT Tony Nguyen
2025-02-04 17:52 ` [PATCH net 1/4] igb: narrow scope of vfs_lock in SR-IOV cleanup Tony Nguyen
2025-02-04 17:52 ` [PATCH net 2/4] igb: introduce raw vfs_lock to igb_adapter Tony Nguyen
2025-02-04 17:52 ` [PATCH net 3/4] igb: split igb_msg_task() Tony Nguyen
2025-02-04 17:52 ` [PATCH net 4/4] igb: fix igb_msix_other() handling for PREEMPT_RT Tony Nguyen
2025-02-05 9:48 ` Sebastian Andrzej Siewior [this message]
2025-02-05 20:08 ` [PATCH net 0/4][pull request] " Wander Lairson Costa
2025-02-06 11:59 ` Sebastian Andrzej Siewior
2025-02-06 20:42 ` Wander Lairson Costa
2025-02-12 11:56 ` Wander Lairson Costa
2025-02-12 15:11 ` Sebastian Andrzej Siewior
2025-02-12 15:21 ` Wander Lairson Costa
2025-02-12 15:29 ` Sebastian Andrzej Siewior
2025-02-18 14:50 ` Wander Lairson Costa
2025-02-19 15:29 ` Steven Rostedt
2025-02-19 15:30 ` Steven Rostedt
2025-02-20 10:52 ` Wander Lairson Costa
2025-02-19 16:41 ` Sebastian Andrzej Siewior
2025-02-20 10:50 ` Wander Lairson Costa
2025-02-19 16:35 ` Sebastian Andrzej Siewior
2025-02-20 11:35 ` Wander Lairson Costa
2025-02-20 11:38 ` Sebastian Andrzej Siewior
2025-03-14 12:12 ` Wander Lairson Costa
2025-03-14 13:16 ` Sebastian Andrzej Siewior
2025-03-14 14:08 ` Wander Lairson Costa
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=20250205094818.I-Jl44AK@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgarzik@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=wander@redhat.com \
--cc=yuma@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;
as well as URLs for NNTP newsgroup(s).