From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, AlvinX" <alvinx.zhang@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: fix DCF Rx segmentation fault
Date: Thu, 29 Oct 2020 05:35:55 +0000 [thread overview]
Message-ID: <3465196c68254285aa53a26ab55a8712@intel.com> (raw)
In-Reply-To: <20201029011322.39392-1-haiyue.wang@intel.com>
> -----Original Message-----
> From: Wang, Haiyue <haiyue.wang@intel.com>
> Sent: Thursday, October 29, 2020 9:13 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Wang, Haiyue
> <haiyue.wang@intel.com>; Zhang, AlvinX <alvinx.zhang@intel.com>; Yang,
> Qiming <qiming.yang@intel.com>; Guo, Jia <jia.guo@intel.com>
> Subject: [PATCH v2] net/ice: fix DCF Rx segmentation fault
>
> The initialization of selecting the handler for scalar Rx path FlexiMD fields
> extraction into mbuf is missed, it will cause segmentation fault (core dumped).
>
> Also add the missed support to handle RXDID 16, which has RSS hash value on
> Qword 1.
>
> Fixes: 7a340b0b4e03 ("net/ice: refactor Rx FlexiMD handling")
>
> Reported-by: Alvin Zhang <alvinx.zhang@intel.com>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel after revert v1
Thanks
Qi
next prev parent reply other threads:[~2020-10-29 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 16:55 [dpdk-dev] [PATCH v1] " Haiyue Wang
2020-10-29 1:13 ` [dpdk-dev] [PATCH v2] " Haiyue Wang
2020-10-29 5:35 ` Zhang, Qi Z [this message]
2020-10-29 1:19 ` [dpdk-dev] [PATCH v1] " 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=3465196c68254285aa53a26ab55a8712@intel.com \
--to=qi.z.zhang@intel.com \
--cc=alvinx.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jia.guo@intel.com \
--cc=qiming.yang@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).