From: "Stillwell Jr, Paul M" <paul.m.stillwell.jr@intel.com>
To: "Su, Simei" <simei.su@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Ye, Xiaolong" <xiaolong.ye@intel.com>,
"Yang, Qiming" <qiming.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Su, Simei" <simei.su@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: fix segmentation fault for RSS init
Date: Wed, 6 Nov 2019 16:10:20 +0000 [thread overview]
Message-ID: <BYAPR11MB38299F572499658FF91E7CE0E0790@BYAPR11MB3829.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1573028777-185130-1-git-send-email-simei.su@intel.com>
Disregard my previous email, I didn't see this one. See my comments inline.
Paul
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Simei Su
> Sent: Wednesday, November 6, 2019 12:26 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Ye, Xiaolong <xiaolong.ye@intel.com>;
> Yang, Qiming <qiming.yang@intel.com>
> Cc: dev@dpdk.org; Su, Simei <simei.su@intel.com>
> Subject: [dpdk-dev] [PATCH v2] net/ice: fix segmentation fault for RSS init
>
> This patch fixes core dump issue when entering safe mode with a wrong
> package file. This patch also fixes build failure issue.
>
> Fixes: 5ad3db8d4bdd ("net/ice: enable advanced RSS")
>
> Signed-off-by: Simei Su <simei.su@intel.com>
> ---
> drivers/net/ice/ice_hash.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ice/ice_hash.c b/drivers/net/ice/ice_hash.c index
> 3381b45..08b2502 100644
> --- a/drivers/net/ice/ice_hash.c
> +++ b/drivers/net/ice/ice_hash.c
> @@ -236,12 +236,12 @@ struct ice_hash_match_type ice_hash_type_list[] = {
> static int ice_hash_init(struct ice_adapter *ad) {
> - struct ice_flow_parser *parser = NULL;
> + struct ice_flow_parser *parser;
>
> - if (ad->active_pkg_type == ICE_PKG_TYPE_OS_DEFAULT)
> - parser = &ice_hash_parser_os;
> - else if (ad->active_pkg_type == ICE_PKG_TYPE_COMMS)
> + if (ad->active_pkg_type == ICE_PKG_TYPE_COMMS)
> parser = &ice_hash_parser_comms;
> + else
> + parser = &ice_hash_parser_os;
This doesn't make sense to me. Why set up a parser at all if we are in safe mode? Safe mode means 1 queue so there isn't anything to RSS to. It seems like if we are in safe mode we should just return an error here with a message that we are in safe mode.
>
> return ice_register_parser(parser, ad); }
> --
> 1.8.3.1
next prev parent reply other threads:[~2019-11-06 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 7:08 [dpdk-dev] [PATCH] " Simei Su
2019-11-06 8:26 ` [dpdk-dev] [PATCH v2] " Simei Su
2019-11-06 16:10 ` Stillwell Jr, Paul M [this message]
2019-11-07 1:06 ` Su, Simei
2019-11-07 5:47 ` [dpdk-dev] [PATCH v3] net/ice: fix segmentation fault with a wrong package Simei Su
2019-11-07 6:14 ` Zhang, Qi Z
2019-11-11 9:06 ` Ye Xiaolong
2019-11-12 4:40 ` Su, Simei
2019-11-13 2:07 ` Ye Xiaolong
2019-11-06 16:03 ` [dpdk-dev] [PATCH] net/ice: fix segmentation fault for RSS init Stillwell Jr, Paul M
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=BYAPR11MB38299F572499658FF91E7CE0E0790@BYAPR11MB3829.namprd11.prod.outlook.com \
--to=paul.m.stillwell.jr@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=simei.su@intel.com \
--cc=xiaolong.ye@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).