[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220317091104.1d911864@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 17 Mar 2022 09:11:04 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jesse Brandeburg <jesse.brandeburg@...el.com>,
Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: Ivan Vecera <ivecera@...hat.com>, netdev@...r.kernel.org,
poros@...hat.com, "David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Slawomir Laba <slawomirx.laba@...el.com>,
Mateusz Palczewski <mateusz.palczewski@...el.com>,
Jacob Keller <jacob.e.keller@...el.com>,
Phani Burra <phani.r.burra@...el.com>,
intel-wired-lan@...ts.osuosl.org (moderated list:INTEL ETHERNET DRIVERS),
linux-kernel@...r.kernel.org (open list)
Subject: Re: [PATCH] iavf: Fix hang during reboot/shutdown
On Thu, 17 Mar 2022 11:45:24 +0100 Ivan Vecera wrote:
> Recent commit 974578017fc1 ("iavf: Add waiting so the port is
> initialized in remove") adds a wait-loop at the beginning of
> iavf_remove() to ensure that port initialization is finished
> prior unregistering net device. This causes a regression
> in reboot/shutdown scenario because in this case callback
> iavf_shutdown() is called and this callback detaches the device,
> makes it down if it is running and sets its state to __IAVF_REMOVE.
> Later shutdown callback of associated PF driver (e.g. ice_shutdown)
> is called. That callback calls among other things sriov_disable()
> that calls indirectly iavf_remove() (see stack trace below).
> As the adapter state is already __IAVF_REMOVE then the mentioned
> loop is end-less and shutdown process hangs.
Tony, Jesse, looks like the regression is from 5.17-rc6, should
I take this directly so it makes 5.17 final?
Powered by blists - more mailing lists