From: "Xu, Ting" <ting.xu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v1] app/testpmd: fix DCB set failure in FreeBSD by clang
Date: Tue, 12 May 2020 02:17:17 +0000 [thread overview]
Message-ID: <d04018dc8e864dee951b7f4bd52ccc6f@intel.com> (raw)
In-Reply-To: <238b76ff-262a-effd-811e-21b58c9b259d@intel.com>
> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Tuesday, May 12, 2020 12:29 AM
> To: Xu, Ting <ting.xu@intel.com>; dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Iremonger, Bernard
> <bernard.iremonger@intel.com>; stable@dpdk.org; Andrew Rybchenko
> <arybchenko@solarflare.com>; Thomas Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] [PATCH v1] app/testpmd: fix DCB set failure in
> FreeBSD by clang
>
> On 5/11/2020 11:25 AM, Ting Xu wrote:
> > When set DCB in testpmd by clang, there is a segmentation fault.
> > It is because the local variable rss_conf in get_eth_dcb_conf() is not
> > cleared, so that the pointer member variable rss_key has a random
> > address, which leads to an error in the following processing. This
> > patch initialized the local variable rss_conf to avoid random address.
>
> This is nothing really FreeBSD or clang issue, although it may be reproduced
> that environment, this is a pointer with random value issue. We may drop
> FreeBSD and clang reference to not create confusion.
>
OK, I will modify the commit log.
> >
> > Fixes: b57b66a97ebf ("app/testpmd: support mbuf dynamic flag")
>
> This commit looks unrelated, if not can you please explain why above
> commit causing the issue?
>
This is the bad commit the validation team find for this issue. Honestly speaking,
I did not find the relation between this commit and the issue either.
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Ting Xu <ting.xu@intel.com>
> > ---
> > app/test-pmd/testpmd.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c index
> > 99bacddbf..1276476ca 100644
> > --- a/app/test-pmd/testpmd.c
> > +++ b/app/test-pmd/testpmd.c
> > @@ -3408,6 +3408,7 @@ get_eth_dcb_conf(portid_t pid, struct
> rte_eth_conf *eth_conf,
> > int32_t rc;
> > struct rte_eth_rss_conf rss_conf;
> >
> > + memset(&rss_conf, 0, sizeof(struct rte_eth_rss_conf));
>
> The variable is used in the 'else' leg, memset can be moved there, but more
> importantly should this be done in the 'rte_eth_dev_rss_hash_conf_get()' API.
>
> @Andrew, @Thomas,
>
> What do you think 'rte_eth_dev_rss_hash_conf_get()' memset the 'rss_conf'
> param before passing it to the PMD? To prevent issues like above in user
> application.
I will move it to the else leg first in the v2 patch. Wait for more comments. Thanks!
next prev parent reply other threads:[~2020-05-12 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 10:25 [dpdk-stable] " Ting Xu
2020-05-11 5:12 ` Xing, Beilei
2020-05-11 7:50 ` [dpdk-stable] [dpdk-dev] " Huang, ZhiminX
2020-05-11 16:29 ` Ferruh Yigit
2020-05-12 2:17 ` Xu, Ting [this message]
2020-05-12 11:42 ` Iremonger, Bernard
2020-05-12 10:13 ` [dpdk-stable] [PATCH v2] app/testpmd: fix DCB set failure Ting Xu
2020-05-18 17:06 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2020-05-13 9:50 ` [dpdk-stable] [PATCH v3] " Ting Xu
2020-05-13 10:07 ` [dpdk-stable] [PATCH v4] " Ting Xu
2020-05-13 8:54 ` [dpdk-stable] [dpdk-dev] " Iremonger, Bernard
2020-05-13 12:58 ` Thomas Monjalon
2020-05-13 17:16 ` [dpdk-stable] [PATCH v5] ethdev: " Ting Xu
2020-05-13 13:28 ` Ferruh Yigit
2020-05-18 16:24 ` Ferruh Yigit
2020-05-13 15:54 ` [dpdk-stable] [dpdk-dev] " Iremonger, Bernard
2020-05-18 13:32 ` Andrew Rybchenko
2020-05-18 14:57 ` Matan Azrad
2020-05-18 16:21 ` Ferruh Yigit
2020-05-18 16:20 ` Ferruh Yigit
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=d04018dc8e864dee951b7f4bd52ccc6f@intel.com \
--to=ting.xu@intel.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@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).