From: Leon Romanovsky <leonro@nvidia.com>
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>,
Dave Ertman <david.m.ertman@intel.com>, <shiraz.saleem@intel.com>,
<mustafa.ismail@intel.com>, <jgg@nvidia.com>,
<linux-rdma@vger.kernel.org>, <poros@redhat.com>,
<ivecera@redhat.com>, <jaroslav.pulchart@gooddata.com>,
<git@sphalerite.org>, <stable@vger.kernel.org>,
Arpana Arland <arpanax.arland@intel.com>
Subject: Re: [PATCH net v3 1/1] ice: avoid bonding causing auxiliary plug/unplug under RTNL lock
Date: Tue, 14 Mar 2023 14:54:07 +0200 [thread overview]
Message-ID: <20230314125407.GD36557@unreal> (raw)
In-Reply-To: <20230310194833.3074601-1-anthony.l.nguyen@intel.com>
On Fri, Mar 10, 2023 at 11:48:33AM -0800, Tony Nguyen 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.
>
> Defer the unplugging/re-plugging of the auxiliary device to the service
> task so that it is not performed under the RTNL lock context.
>
> Cc: stable@vger.kernel.org # 6.1.x
> Reported-by: Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>
> Link: https://lore.kernel.org/netdev/CAK8fFZ6A_Gphw_3-QMGKEFQk=sfCw1Qmq0TVZK3rtAi7vb621A@mail.gmail.com/
> Fixes: 5cb1ebdbc434 ("ice: Fix race condition during interface enslave")
> Fixes: 4eace75e0853 ("RDMA/irdma: Report the correct link speed")
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
> Tested-by: Arpana Arland <arpanax.arland@intel.com> (A Contingent worker at Intel)
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> Note:
> This was reported as still causing issues [1], however, with details from
> the reporter we have not been able to reproduce the issue; a newer
> firmware was reported to fix their problem [2]. As this fixes the bug for
> other users [3][4], I'm submitting this patch.
>
> v3:
> - Add Tested-by
>
> v2: https://lore.kernel.org/netdev/20230217004201.2895321-1-anthony.l.nguyen@intel.com/
> (Removed from original pull request)
> - Reversed order of bit processing in ice_service_task for PLUG/UNPLUG
>
> v1: https://lore.kernel.org/netdev/20230131213703.1347761-2-anthony.l.nguyen@intel.com/
>
> [1] https://lore.kernel.org/intel-wired-lan/ygay1oxikvo.fsf@localhost/
> [2] https://lore.kernel.org/intel-wired-lan/ygattz3tjk9.fsf@localhost/
> [3] https://lore.kernel.org/netdev/CAK8fFZ5Jjh-ZXfLdupQGqvb9pg7nW-6fWMN3cPMdmQQfQRLGFA@mail.gmail.com/
> [4] https://lore.kernel.org/intel-wired-lan/16c393e17c552cbf0c3456194456d32ea8bc826a.camel@redhat.com/
>
> drivers/net/ethernet/intel/ice/ice.h | 14 +++++---------
> drivers/net/ethernet/intel/ice/ice_main.c | 19 ++++++++-----------
> 2 files changed, 13 insertions(+), 20 deletions(-)
>
Thanks,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2023-03-14 13:04 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 [this message]
2023-03-15 7:10 ` 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=20230314125407.GD36557@unreal \
--to=leonro@nvidia.com \
--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=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.