From: Simon Horman <horms@kernel.org>
To: Karen Ostrowska <karen.ostrowska@intel.com>
Cc: intel-wired-lan@lists.osuosl.org,
Eric Joyner <eric.joyner@intel.com>,
netdev@vger.kernel.org,
Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: Re: [iwl-next v1] ice: Check all ice_vsi_rebuild() errors in function
Date: Tue, 4 Jun 2024 15:47:12 +0100 [thread overview]
Message-ID: <20240604144712.GR491852@kernel.org> (raw)
In-Reply-To: <20240528090140.221964-1-karen.ostrowska@intel.com>
On Tue, May 28, 2024 at 11:01:40AM +0200, Karen Ostrowska wrote:
> From: Eric Joyner <eric.joyner@intel.com>
>
> Check the return value from ice_vsi_rebuild() and prevent the usage of
> incorrectly configured VSI.
>
> Reviewed-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Eric Joyner <eric.joyner@intel.com>
> Signed-off-by: Karen Ostrowska <karen.ostrowska@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_main.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
> index f60c022f7960..e8c30b1730a6 100644
> --- a/drivers/net/ethernet/intel/ice/ice_main.c
> +++ b/drivers/net/ethernet/intel/ice/ice_main.c
> @@ -4135,15 +4135,23 @@ int ice_vsi_recfg_qs(struct ice_vsi *vsi, int new_rx, int new_tx, bool locked)
>
> /* set for the next time the netdev is started */
> if (!netif_running(vsi->netdev)) {
> - ice_vsi_rebuild(vsi, ICE_VSI_FLAG_NO_INIT);
> + err = ice_vsi_rebuild(vsi, ICE_VSI_FLAG_NO_INIT);
> + if (err)
> + goto rebuild_err;
> dev_dbg(ice_pf_to_dev(pf), "Link is down, queue count change happens when link is brought up\n");
> goto done;
> }
>
> ice_vsi_close(vsi);
> - ice_vsi_rebuild(vsi, ICE_VSI_FLAG_NO_INIT);
> + err = ice_vsi_rebuild(vsi, ICE_VSI_FLAG_NO_INIT);
> + if (err)
> + goto rebuild_err;
> +
> ice_pf_dcb_recfg(pf, locked);
> ice_vsi_open(vsi);
Hi Karen,
This seems to be a good improvement to me, thanks.
But I do winder if we can go a bit further:
* Should the return value of ice_vsi_open() also be checked?
* Should the return value of ice_vsi_recfg_qs() be checked?
Also, I think the following is appropriate here:
goto done;
> +
> +rebuild_err:
> + dev_err(ice_pf_to_dev(pf), "Error during VSI rebuild: %d. Unload and reload the driver.\n", err);
> done:
> clear_bit(ICE_CFG_BUSY, pf->state);
> return err;
> --
> 2.31.1
>
>
next prev parent reply other threads:[~2024-06-04 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 9:01 [iwl-next v1] ice: Check all ice_vsi_rebuild() errors in function Karen Ostrowska
2024-05-29 17:09 ` [Intel-wired-lan] " Pucha, HimasekharX Reddy
2024-06-14 7:37 ` Larysa Zaremba
2024-06-04 14:47 ` Simon Horman [this message]
2024-06-05 13:51 ` Ostrowska, Karen
2024-06-11 9:01 ` [Intel-wired-lan] " Paul Menzel
2024-06-14 7:33 ` Larysa Zaremba
-- strict thread matches above, loose matches on Subject: below --
2024-05-28 8:52 Karen Ostrowska
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=20240604144712.GR491852@kernel.org \
--to=horms@kernel.org \
--cc=eric.joyner@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karen.ostrowska@intel.com \
--cc=michal.swiatkowski@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@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).