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: Thu, 18 May 2023 14:28:57 -0700 [thread overview]
Message-ID: <e6e668ac-8175-ea5c-25c2-65bcfa60eca6@intel.com> (raw)
In-Reply-To: <73793dcb-c47e-41c0-e34c-a9de5258d385@intel.com>
On 4/19/2023 11:42 AM, Jacob Keller wrote:
>
>
> 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;
Wait. We must not modify netdev->flags like this. Please do not restore
this part of the commit. Perhaps a new commit message with a partial
revert explanation. Modification of the netdev flags like this is incorrect.
See the original commit message which said:
Also replace the hacky manipulation with IFF_UP flag by device close
that clears properly both IFF_UP and __LINK_STATE_START flags.
In these case iavf_close() does not do anything because the adapter
state is already __IAVF_DOWN.
NAK this change as-is.
It may be no longer required to perform the other parts of the patch,
but I do not accept re-adding the incorrect IFF_UP modification.
Thanks,
Jake
_______________________________________________
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-05-18 21:29 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
2023-05-18 21:28 ` Jacob Keller [this message]
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=e6e668ac-8175-ea5c-25c2-65bcfa60eca6@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