From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Patil, Harish" <Harish.Patil@cavium.com>,
Rongqiang XIE <xie.rongqiang@zte.com.cn>,
"Mody, Rasesh" <Rasesh.Mody@cavium.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/qede:fix the bug about pointer params may NULL
Date: Mon, 28 Aug 2017 13:42:43 +0100 [thread overview]
Message-ID: <a4ae1b58-4f51-2aa8-8c68-86c5a846ad1f@intel.com> (raw)
In-Reply-To: <D5C5BCFE.15B4DF%Harish.Patil@cavium.com>
On 8/25/2017 7:43 PM, Patil, Harish wrote:
<..>>
> Subject: [dpdk-dev] [PATCH] net/qede:fix the bug about pointer params
> may NULL
>
>> In function qede_rss_reta_update(),the pointer params returned from
>> call to function rte_zmalloc() may be NULL and will be dereferenced.
>> So, should judge the params is NULL or not.
Fixes: 8b3ee85efe11 ("net/qede: fix RSS table entries for 100G adapter")
Cc: stable@dpdk.org
>>
>> Signed-off-by: Rongqiang XIE <xie.rongqiang@zte.com.cn>
>> Acked-by: Harish Patil <harish.patil@cavium.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-08-28 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 7:12 Rongqiang XIE
2017-08-25 18:43 ` Patil, Harish
2017-08-28 12:42 ` Ferruh Yigit [this message]
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=a4ae1b58-4f51-2aa8-8c68-86c5a846ad1f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=Harish.Patil@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=dev@dpdk.org \
--cc=xie.rongqiang@zte.com.cn \
/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).