From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
andrew+netdev@lunn.ch, netdev@vger.kernel.org,
Ahmed Zaki <ahmed.zaki@intel.com>,
willemb@google.com, Madhu Chittim <madhu.chittim@intel.com>,
Simon Horman <horms@kernel.org>,
Samuel Salin <Samuel.salin@intel.com>
Subject: Re: [PATCH net 3/5] idpf: synchronize pending IRQs after disable
Date: Tue, 25 Feb 2025 18:38:44 -0800 [thread overview]
Message-ID: <20250225183844.44f9eb66@kernel.org> (raw)
In-Reply-To: <20250224190647.3601930-4-anthony.l.nguyen@intel.com>
On Mon, 24 Feb 2025 11:06:43 -0800 Tony Nguyen wrote:
> From: Ahmed Zaki <ahmed.zaki@intel.com>
>
> Wait for pending IRQ handler after it is disabled. This will ensure the IRQ
> is cleanly freed afterwards.
No real explanation of the race in the commit message, no comment
in the code. More info needed here.
next prev parent reply other threads:[~2025-02-26 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 19:06 [PATCH net 0/5][pull request] Intel Wired LAN Driver Updates 2025-02-24 (ice, idpf, iavf, ixgbe) Tony Nguyen
2025-02-24 19:06 ` [PATCH net 1/5] ice: Fix deinitializing VF in error path Tony Nguyen
2025-02-24 19:06 ` [PATCH net 2/5] ice: Avoid setting default Rx VSI twice in switchdev setup Tony Nguyen
2025-02-24 19:06 ` [PATCH net 3/5] idpf: synchronize pending IRQs after disable Tony Nguyen
2025-02-26 2:38 ` Jakub Kicinski [this message]
2025-02-26 18:16 ` Tony Nguyen
2025-02-24 19:06 ` [PATCH net 4/5] iavf: fix circular lock dependency with netdev_lock Tony Nguyen
2025-02-24 19:06 ` [PATCH net 5/5] ixgbe: fix media cage present detection for E610 device Tony Nguyen
2025-02-26 3:20 ` [PATCH net 0/5][pull request] Intel Wired LAN Driver Updates 2025-02-24 (ice, idpf, iavf, ixgbe) patchwork-bot+netdevbpf
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=20250225183844.44f9eb66@kernel.org \
--to=kuba@kernel.org \
--cc=Samuel.salin@intel.com \
--cc=ahmed.zaki@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 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.