From: "Singh, Aman Deep" <aman.deep.singh@intel.com>
To: <wenxuanx.wu@intel.com>, <xiaoyun.li@intel.com>
Cc: <dev@dpdk.org>, <junfeng.guo@intel.com>, <qiming.yang@intel.com>
Subject: Re: [PATCH] app/testpmd : fix testpmd quit error
Date: Fri, 11 Feb 2022 12:42:37 +0530 [thread overview]
Message-ID: <eae78b5f-0eac-0c23-9eaa-b0316eb894d4@intel.com> (raw)
In-Reply-To: <20220209104243.117334-1-wenxuanx.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1708 bytes --]
Hi Wenxuan Wu,
On 2/9/2022 4:12 PM, wenxuanx.wu@intel.com wrote:
> From: Wenxuan Wu<wenxuanx.wu@intel.com>
>
> when testpmd startup with pf and vfs, it is ok when running, while
> exiting, it will result in heap-free-after-use which means pf is
> released but vf is still accessing.
>
> Change the logic of func port_is_bonding_slave ,this func
> eth_dev_info_get_print_err while pf is released would result in this error.
Removing call to func eth_dev_info_get_print_err, seems like a quick fix to the problem.
Can you try root causing further, where pf is released. And can the order be fixed,
first free vf and then the pf.
>
> Fixes: 0a0821bcf312 ("app/testpmd: remove most uses of internal ethdev array")
> Cc:stable@dpdk.org
>
> Signed-off-by: Wenxuan Wu<wenxuanx.wu@intel.com>
> ---
> app/test-pmd/testpmd.c | 13 ++-----------
> 1 file changed, 2 insertions(+), 11 deletions(-)
>
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index e1da961311..7fa1944d78 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -3824,19 +3824,10 @@ void clear_port_slave_flag(portid_t slave_pid)
> uint8_t port_is_bonding_slave(portid_t slave_pid)
> {
> struct rte_port *port;
> - struct rte_eth_dev_info dev_info;
> - int ret;
>
> port = &ports[slave_pid];
> - ret = eth_dev_info_get_print_err(slave_pid, &dev_info);
> - if (ret != 0) {
> - TESTPMD_LOG(ERR,
> - "Failed to get device info for port id %d,"
> - "cannot determine if the port is a bonded slave",
> - slave_pid);
> - return 0;
> - }
> - if ((*dev_info.dev_flags & RTE_ETH_DEV_BONDED_SLAVE) || (port->slave_flag == 1))
> +
> + if (port->slave_flag == 1)
> return 1;
> return 0;
> }
[-- Attachment #2: Type: text/html, Size: 2477 bytes --]
next prev parent reply other threads:[~2022-02-11 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:42 wenxuanx.wu
2022-02-11 7:12 ` Singh, Aman Deep [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-09 10:38 wenxuanx.wu
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=eae78b5f-0eac-0c23-9eaa-b0316eb894d4@intel.com \
--to=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=junfeng.guo@intel.com \
--cc=qiming.yang@intel.com \
--cc=wenxuanx.wu@intel.com \
--cc=xiaoyun.li@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).