From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
david.m.ertman@intel.com, shiraz.saleem@intel.com,
mustafa.ismail@intel.com, jgg@nvidia.com, leonro@nvidia.com,
linux-rdma@vger.kernel.org, poros@redhat.com, ivecera@redhat.com,
jaroslav.pulchart@gooddata.com, git@sphalerite.org,
stable@vger.kernel.org, arpanax.arland@intel.com
Subject: Re: [PATCH net v3 1/1] ice: avoid bonding causing auxiliary plug/unplug under RTNL lock
Date: Wed, 15 Mar 2023 07:10:16 +0000 [thread overview]
Message-ID: <167886421661.23656.18355961550243995627.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230310194833.3074601-1-anthony.l.nguyen@intel.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 Mar 2023 11:48:33 -0800 you wrote:
> From: Dave Ertman <david.m.ertman@intel.com>
>
> RDMA is not supported in ice on a PF that has been added to a bonded
> interface. To enforce this, when an interface enters a bond, we unplug
> the auxiliary device that supports RDMA functionality. This unplug
> currently happens in the context of handling the netdev bonding event.
> This event is sent to the ice driver under RTNL context. This is causing
> a deadlock where the RDMA driver is waiting for the RTNL lock to complete
> the removal.
>
> [...]
Here is the summary with links:
- [net,v3,1/1] ice: avoid bonding causing auxiliary plug/unplug under RTNL lock
https://git.kernel.org/netdev/net/c/248401cb2c46
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-15 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 19:48 [PATCH net v3 1/1] ice: avoid bonding causing auxiliary plug/unplug under RTNL lock Tony Nguyen
2023-03-14 12:54 ` Leon Romanovsky
2023-03-15 7:10 ` patchwork-bot+netdevbpf [this message]
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=167886421661.23656.18355961550243995627.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=arpanax.arland@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=git@sphalerite.org \
--cc=ivecera@redhat.com \
--cc=jaroslav.pulchart@gooddata.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=shiraz.saleem@intel.com \
--cc=stable@vger.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.