From: Jacob Keller <jacob.e.keller@intel.com>
To: Petr Oros <poros@redhat.com>, <netdev@vger.kernel.org>
Cc: <jesse.brandeburg@intel.com>, <anthony.l.nguyen@intel.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <przemyslawx.patynowski@intel.com>,
<kamil.maziarz@intel.com>, <dawidx.wesierski@intel.com>,
<mateusz.palczewski@intel.com>, <slawomirx.laba@intel.com>,
<norbertx.zulinski@intel.com>, <intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 0/2] Fix VF to VM attach detach
Date: Tue, 8 Aug 2023 15:10:59 -0700 [thread overview]
Message-ID: <9ec85f45-4724-4695-a853-16c5efcf8151@intel.com> (raw)
In-Reply-To: <20230807094831.696626-1-poros@redhat.com>
On 8/7/2023 2:48 AM, Petr Oros wrote:
> Petr Oros (2):
> Revert "ice: Fix ice VF reset during iavf initialization"
> ice: Fix NULL pointer deref during VF reset
>
> drivers/net/ethernet/intel/ice/ice_sriov.c | 8 ++---
> drivers/net/ethernet/intel/ice/ice_vf_lib.c | 34 +++++--------------
> drivers/net/ethernet/intel/ice/ice_vf_lib.h | 1 -
> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 1 -
> 4 files changed, 12 insertions(+), 32 deletions(-)
>
I reviewed the commit message for the reverted commit and I concur that
any sort of issue that it fixed with respect to concurrent resets is
better fixed by the 2nd commit of this series.
The motivation for the original commit appears to be to prevent a reset
from happening while the VF is still resetting. I think this motivation
is incorrect for a few reasons:
1) as described by the revert above, if the VF has not had iAVF load on
it yet (such as when its been assigned to the pass through PCI driver),
it will never initialize, and thus we can't ever reset the device.
2) It does not make sense for the PF to rely on or assume behavior of
the VF (i.e. that it will properly initialize) and I believe it should
be allowed to reset the device without regard to the state of the VF
driver. It is a bug in the VF driver if this causes problems for it. I
think we recently fixed several issues here in iAVF.
With that in mind, I think this series of fixes is good.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
prev parent reply other threads:[~2023-08-08 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 9:48 [PATCH net 0/2] Fix VF to VM attach detach Petr Oros
2023-08-07 9:48 ` [PATCH net 1/2] Revert "ice: Fix ice VF reset during iavf initialization" Petr Oros
2023-08-08 12:51 ` Simon Horman
2023-08-07 9:48 ` [PATCH net 2/2] ice: Fix NULL pointer deref during VF reset Petr Oros
2023-08-08 12:51 ` Simon Horman
2023-08-08 20:54 ` [Intel-wired-lan] " Przemek Kitszel
2023-08-09 18:14 ` Petr Oros
2023-08-08 20:56 ` [Intel-wired-lan] [PATCH net 0/2] Fix VF to VM attach detach Przemek Kitszel
2023-08-08 22:10 ` Jacob Keller [this message]
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=9ec85f45-4724-4695-a853-16c5efcf8151@intel.com \
--to=jacob.e.keller@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dawidx.wesierski@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kamil.maziarz@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mateusz.palczewski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=norbertx.zulinski@intel.com \
--cc=pabeni@redhat.com \
--cc=poros@redhat.com \
--cc=przemyslawx.patynowski@intel.com \
--cc=slawomirx.laba@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).