From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v4] net/ice: fix crash on closing representor ports
Date: Mon, 6 Nov 2023 01:23:10 +0000 [thread overview]
Message-ID: <DM4PR11MB5994405D3B94A052984CDE19D7AAA@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231102101103.3707173-1-mingjinx.ye@intel.com>
> -----Original Message-----
> From: Ye, MingjinX <mingjinx.ye@intel.com>
> Sent: Thursday, November 2, 2023 6:11 PM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhou, YidingX
> <yidingx.zhou@intel.com>; Ye, MingjinX <mingjinx.ye@intel.com>;
> stable@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: [PATCH v4] net/ice: fix crash on closing representor ports
>
> Since the representor port needs to access the resource of the associated DCF
> when it is closing. Therefore, all the representor port should be closed first,
> and then close the associated DCF port.
>
> If the DCF port is closed before the representor port on PMD exit.
> This will result in accessing freed resources and eventually a core dump will
> occur.
>
> This patch fixes this issue by notifying each other to unassociate when the
> DCF port and the representor port are closed.
>
> Fixes: 5674465a32c8 ("net/ice: add DCF VLAN handling")
> Fixes: c7e1a1a3bfeb ("net/ice: refactor DCF VLAN handling")
> Fixes: da9cdcd1f372 ("net/ice: fix crash on representor port closing")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
> v2: Reformat code to remove unneeded fixlines.
> ---
> v3: New solution.
> ---
> v4: Optimize v2 patch.
> ---
> drivers/net/ice/ice_dcf_ethdev.c | 20 ++++++++++++++++++++
> drivers/net/ice/ice_dcf_ethdev.h | 2 ++
> drivers/net/ice/ice_dcf_vf_representor.c | 23 ++++++++++++++++++-----
> 3 files changed, 40 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/ice/ice_dcf_ethdev.c b/drivers/net/ice/ice_dcf_ethdev.c
> index 065ec728c2..63e63a23de 100644
> --- a/drivers/net/ice/ice_dcf_ethdev.c
> +++ b/drivers/net/ice/ice_dcf_ethdev.c
> @@ -1618,6 +1618,26 @@ ice_dcf_free_repr_info(struct ice_dcf_adapter
> *dcf_adapter)
> }
> }
>
> +int
> +ice_dcf_handle_vf_repr_uninit(struct ice_dcf_adapter *dcf_adapter,
> + uint16_t vf_id)
> +{
> + struct ice_dcf_repr_info *vf_rep_info;
> +
> + if (dcf_adapter->num_reprs >= vf_id) {
> + PMD_DRV_LOG(ERR, "Invalid VF id: %d", vf_id);
> + return -1;
> + }
> +
> + if (!dcf_adapter->repr_infos)
> + return 0;
> +
> + vf_rep_info = &dcf_adapter->repr_infos[vf_id];
> + vf_rep_info->vf_rep_eth_dev = NULL;
> +
> + return 0;
> +}
> +
> static int
> ice_dcf_init_repr_info(struct ice_dcf_adapter *dcf_adapter) { diff --git
> a/drivers/net/ice/ice_dcf_ethdev.h b/drivers/net/ice/ice_dcf_ethdev.h
> index 4baaec4b8b..094e2a36db 100644
> --- a/drivers/net/ice/ice_dcf_ethdev.h
> +++ b/drivers/net/ice/ice_dcf_ethdev.h
> @@ -60,6 +60,7 @@ struct ice_dcf_vf_repr {
> struct rte_ether_addr mac_addr;
> uint16_t switch_domain_id;
> uint16_t vf_id;
> + bool dcf_valid;
>
> struct ice_dcf_vlan outer_vlan_info; /* DCF always handle outer VLAN
> */ }; @@ -81,5 +82,6 @@ int ice_dcf_vf_repr_uninit(struct rte_eth_dev
> *vf_rep_eth_dev); int ice_dcf_vf_repr_init_vlan(struct rte_eth_dev
> *vf_rep_eth_dev); void ice_dcf_vf_repr_stop_all(struct ice_dcf_adapter
> *dcf_adapter); bool ice_dcf_adminq_need_retry(struct ice_adapter *ad);
> +int ice_dcf_handle_vf_repr_uninit(struct ice_dcf_adapter *dcf_adapter,
> +uint16_t vf_id);
>
> #endif /* _ICE_DCF_ETHDEV_H_ */
> diff --git a/drivers/net/ice/ice_dcf_vf_representor.c
> b/drivers/net/ice/ice_dcf_vf_representor.c
> index b9fcfc80ad..167abaa780 100644
> --- a/drivers/net/ice/ice_dcf_vf_representor.c
> +++ b/drivers/net/ice/ice_dcf_vf_representor.c
> @@ -45,6 +45,9 @@ ice_dcf_vf_repr_dev_start(struct rte_eth_dev *dev)
> static int ice_dcf_vf_repr_dev_stop(struct rte_eth_dev *dev) {
> + struct ice_dcf_vf_repr *repr = dev->data->dev_private;
> +
> + repr->dcf_valid = false;
Is this correct ?
ice_dcf_handle_vf_repr_uninit will not be called,
if we stop a representor port (call ice_dcf_vf_repr_dev_stop), then close it (call ice_dcf_vf_repr_uninit) while DCF still be active.
if you want to use dcf_valid as a notification flag sent from dcf to each representors, never set it in a representer's own callback function.
Btw, besides set dcf_valid to true in ice_dcf_vf_repr_init, you may also consider the case when a DCF reset happen, dcf_valid need to be reset to true for each active representor.
...
> *init_param) int ice_dcf_vf_repr_uninit(struct rte_eth_dev *vf_rep_eth_dev)
> {
> + struct ice_dcf_vf_repr *repr = vf_rep_eth_dev->data->dev_private;
> + struct ice_dcf_adapter *dcf_adapter;
> +
> + if (repr->dcf_valid) {
> + dcf_adapter = repr->dcf_eth_dev->data->dev_private;
> + ice_dcf_handle_vf_repr_uninit(dcf_adapter, repr->vf_id);
> + }
> +
> vf_rep_eth_dev->data->mac_addrs = NULL;
>
> return 0;
next prev parent reply other threads:[~2023-11-06 1:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:51 [PATCH] net/iavf: " Mingjin Ye
2023-10-27 7:17 ` David Marchand
2023-10-30 2:35 ` [PATCH v2] " Mingjin Ye
2023-10-30 8:44 ` [PATCH v2] net/ice: " Mingjin Ye
2023-11-01 1:11 ` Zhang, Qi Z
2023-11-01 10:13 ` [PATCH v3] " Mingjin Ye
2023-11-01 10:48 ` Zhang, Qi Z
2023-11-02 2:38 ` Ye, MingjinX
2023-11-02 3:59 ` Zhang, Qi Z
2023-11-02 10:11 ` [PATCH v4] " Mingjin Ye
2023-11-06 1:23 ` Zhang, Qi Z [this message]
2023-11-06 10:00 ` [PATCH v5] " Mingjin Ye
2023-11-06 12:05 ` Zhang, Qi Z
2023-11-07 10:12 ` [PATCH v6] " Mingjin Ye
2023-11-07 12:18 ` Zhang, Qi Z
2023-11-08 11:39 ` [PATCH v7] " Mingjin Ye
2023-11-09 0:26 ` Zhang, Qi Z
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=DM4PR11MB5994405D3B94A052984CDE19D7AAA@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=mingjinx.ye@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@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).