From: "Xu, Rosen" <rosen.xu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Zhang, Tianfei" <tianfei.zhang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Huang, Wei" <wei.huang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/1] raw/ifpga/base: check size before assigning
Date: Tue, 20 Apr 2021 01:59:49 +0000 [thread overview]
Message-ID: <BYAPR11MB29012192B633865BCA6C39E289489@BYAPR11MB2901.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a6f70ac3-6821-c128-6752-a4e85f8079f1@intel.com>
Thanks all.
-----Original Message-----
From: Yigit, Ferruh <ferruh.yigit@intel.com>
Sent: Tuesday, April 20, 2021 9:01 AM
To: Zhang, Tianfei <tianfei.zhang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Huang, Wei <wei.huang@intel.com>; dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH v2 1/1] raw/ifpga/base: check size before assigning
On 4/20/2021 1:13 AM, Zhang, Tianfei wrote:
>
>
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: 2021年4月20日 6:36
>> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Huang, Wei
>> <wei.huang@intel.com>; dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>
>> Cc: stable@dpdk.org; Zhang, Tianfei <tianfei.zhang@intel.com>
>> Subject: Re: [PATCH v2 1/1] raw/ifpga/base: check size before
>> assigning
>>
>> On 4/19/2021 9:12 AM, Zhang, Qi Z wrote:
>>>
>>>
>>>> -----Original Message-----
>>>> From: Huang, Wei <wei.huang@intel.com>
>>>> Sent: Thursday, April 8, 2021 4:52 PM
>>>> To: dev@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Qi Z
>>>> <qi.z.zhang@intel.com>
>>>> Cc: stable@dpdk.org; Zhang, Tianfei <tianfei.zhang@intel.com>;
>>>> Yigit, Ferruh <ferruh.yigit@intel.com>; Huang, Wei
>>>> <wei.huang@intel.com>
>>>> Subject: [PATCH v2 1/1] raw/ifpga/base: check size before assigning
>>>>
>>>> In max10_staging_area_init(), variable "size" from fdt_get_reg()
>>>> may be invalid, it should be checked before assigning to member
>>>> variable
>> "staging_area_size"
>>>> of structure "intel_max10_device".
>>>>
>>>> Coverity issue: 367480, 367482
>>>> Fixes: 96ebfcf8125c ("raw/ifpga/base: add SPI and MAX10 device
>>>> driver")
>>>>
>>>> Signed-off-by: Wei Huang <wei.huang@intel.com>
>>>> ---
>>>
>>> Applied to dpdk-next-net-intel.
>>>
>>
>> This patch is missing the maintainer ack.
>>
>> Rosen, Tianfei, can you please review the patch?
>
> It looks good for me.
>
> Acked-by: Tianfei zhang <Tianfei.zhang@intel.com>
>
Thanks, added in next-net.
prev parent reply other threads:[~2021-04-20 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 8:51 [dpdk-dev] [PATCH v2 0/1] Fix coverity issues reported in DPDK-26381 Wei Huang
2021-04-08 8:51 ` [dpdk-dev] [PATCH v2 1/1] raw/ifpga/base: check size before assigning Wei Huang
2021-04-08 9:38 ` Ferruh Yigit
2021-04-09 14:56 ` Aaron Conole
2021-04-14 2:46 ` Zhang, Tianfei
2021-04-14 7:42 ` Ferruh Yigit
2021-04-16 2:49 ` Huang, Wei
2021-05-17 8:50 ` Ferruh Yigit
2021-04-19 8:12 ` Zhang, Qi Z
2021-04-19 22:35 ` Ferruh Yigit
2021-04-20 0:13 ` Zhang, Tianfei
2021-04-20 1:00 ` Ferruh Yigit
2021-04-20 1:59 ` Xu, Rosen [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=BYAPR11MB29012192B633865BCA6C39E289489@BYAPR11MB2901.namprd11.prod.outlook.com \
--to=rosen.xu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=tianfei.zhang@intel.com \
--cc=wei.huang@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).