From: Ivan Vecera <ivecera@redhat.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net] ice: Fix race condition during interface enslave
Date: Thu, 10 Mar 2022 19:06:42 +0100 [thread overview]
Message-ID: <20220310190642.556063ae@ceranb> (raw)
In-Reply-To: <MW5PR11MB58114999381C7B98598BB568DD0B9@MW5PR11MB5811.namprd11.prod.outlook.com>
On Thu, 10 Mar 2022 17:48:16 +0000
"Ertman, David M" <david.m.ertman@intel.com> wrote:
> This only addresses one case of unplugging the auxiliary bus. Rather than controlling one instance of
> calling ice_unplig_aux_dev(), it seems like it would be better to modify ice_unplug_aux_dev so that it
> will pause until any plugging is done by the service task (check for the pf->flag bit and wait until it clears
> before progressing).
You cannot wait in ice_unplug_aux_dev() for ICE_FLAG_PLUG_AUX_DEV to be cleared because
ice_clear_rdma_cap() is called under RTNL.
This patch is a counter part for commit 5dbbbd01cbba83 ("ice: Avoid RTNL lock when
re-creating auxiliary device") that eliminates ice_plug_aux() and fixed first part
of deadlock and this patch fixes a second part and eliminates also ice_unplug_aux_dev()
to be called under RTNL.
Thanks,
Ivan
next prev parent reply other threads:[~2022-03-10 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 17:16 [Intel-wired-lan] [PATCH net] ice: Fix race condition during interface enslave Ivan Vecera
2022-03-10 17:48 ` Ertman, David M
2022-03-10 18:06 ` Ivan Vecera [this message]
2022-03-10 19:26 ` Ertman, David M
2022-03-10 21:59 ` Jakub Kicinski
2022-03-10 22:15 ` Tony Nguyen
2022-03-10 23:30 ` 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=20220310190642.556063ae@ceranb \
--to=ivecera@redhat.com \
--cc=intel-wired-lan@osuosl.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.