From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH net v3 4/4] Revert "iavf: Do not restart Tx queues after reset task failure"
Date: Wed, 19 Apr 2023 11:42:11 -0700 [thread overview]
Message-ID: <73793dcb-c47e-41c0-e34c-a9de5258d385@intel.com> (raw)
In-Reply-To: <20230419115006.200409-5-kamil.maziarz@intel.com>
On 4/19/2023 4:50 AM, Kamil Maziarz wrote:
> From: Marcin Szycik <marcin.szycik@linux.intel.com>
>
> This reverts commit 08f1c147b7265245d67321585c68a27e990e0c4b.
>
> Netdev is no longer being detached during reset, so this fix can be
> reverted.
>
> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Signed-off-by: Kamil Maziarz <kamil.maziarz@intel.com>
With the other fixes, this is good.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> ---
> v2: no changes
> ---
> v3: no changes
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 16 +---------------
> 1 file changed, 1 insertion(+), 15 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
> index 8dd488158961..8f13685ed2fe 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_main.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
> @@ -2988,6 +2988,7 @@ static void iavf_disable_vf(struct iavf_adapter *adapter)
> iavf_free_queues(adapter);
> memset(adapter->vf_res, 0, IAVF_VIRTCHNL_VF_RESOURCE_SIZE);
> iavf_shutdown_adminq(&adapter->hw);
> + adapter->netdev->flags &= ~IFF_UP;
> adapter->flags &= ~IAVF_FLAG_RESET_PENDING;
> iavf_change_state(adapter, __IAVF_DOWN);
> wake_up(&adapter->down_waitqueue);
> @@ -3082,11 +3083,6 @@ static void iavf_reset_task(struct work_struct *work)
> iavf_disable_vf(adapter);
> mutex_unlock(&adapter->client_lock);
> mutex_unlock(&adapter->crit_lock);
> - if (netif_running(netdev)) {
> - rtnl_lock();
> - dev_close(netdev);
> - rtnl_unlock();
> - }
> return; /* Do not attempt to reinit. It's dead, Jim. */
> }
>
> @@ -3237,16 +3233,6 @@ static void iavf_reset_task(struct work_struct *work)
>
> mutex_unlock(&adapter->client_lock);
> mutex_unlock(&adapter->crit_lock);
> -
> - if (netif_running(netdev)) {
> - /* Close device to ensure that Tx queues will not be started
> - * during netif_device_attach() at the end of the reset task.
> - */
> - rtnl_lock();
> - dev_close(netdev);
> - rtnl_unlock();
> - }
> -
> dev_err(&adapter->pdev->dev, "failed to allocate resources during reinit\n");
> }
>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-04-19 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:50 [Intel-wired-lan] [PATCH net v3 0/4] iavf: fix reset task deadlock Kamil Maziarz
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 1/4] iavf: Wait for reset in callbacks which trigger it Kamil Maziarz
2023-04-19 18:36 ` Jacob Keller
2023-04-19 22:47 ` Tony Nguyen
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 2/4] iavf: Don't lock rtnl_lock twice in reset Kamil Maziarz
2023-04-19 18:40 ` Jacob Keller
2023-04-19 22:48 ` Tony Nguyen
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 3/4] Revert "iavf: Detach device during reset task" Kamil Maziarz
2023-04-19 18:41 ` Jacob Keller
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 4/4] Revert "iavf: Do not restart Tx queues after reset task failure" Kamil Maziarz
2023-04-19 18:42 ` Jacob Keller [this message]
2023-05-18 21:28 ` Jacob Keller
2023-04-19 18:35 ` [Intel-wired-lan] [PATCH net v3 0/4] iavf: fix reset task deadlock Jacob Keller
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=73793dcb-c47e-41c0-e34c-a9de5258d385@intel.com \
--to=jacob.e.keller@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox