From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Kozak, KubaX" <kubax.kozak@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/e1000: fix out of bounds access
Date: Mon, 31 Jul 2017 13:06:53 +0100 [thread overview]
Message-ID: <2f01d8a2-a484-6d8b-43c3-41f011a9c8ac@intel.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09093B67B531@shsmsx102.ccr.corp.intel.com>
On 7/25/2017 2:24 PM, Lu, Wenzhuo wrote:
> Hi Kuba,
>
>> -----Original Message-----
>> From: Kozak, KubaX
>> Sent: Tuesday, July 25, 2017 8:19 AM
>> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>
>> Cc: dev@dpdk.org; Jain, Deepak K <deepak.k.jain@intel.com>; Jastrzebski,
>> MichalX K <michalx.k.jastrzebski@intel.com>; Kozak, KubaX
>> <kubax.kozak@intel.com>; stable@dpdk.org
>> Subject: [PATCH] net/e1000: fix out of bounds access
>>
>> Fix wrong structure type used as argument in memset() call.
>>
>> Coverity issue: 147223
>> Coverity issue: 147227
> I'm not sure what's this "coverity issue" mean. Maybe we can remove it?
> Except that, Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
>
>> Fixes: a8600af43738 ("net/igb: parse flow API ethertype filter")
>> Fixes: 22bb13410cb2 ("net/igb: create consistent filter")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Kuba Kozak <kubax.kozak@intel.com>
Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-07-31 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 12:19 Kuba Kozak
2017-07-25 13:24 ` Lu, Wenzhuo
2017-07-25 13:35 ` Jastrzebski, MichalX K
2017-07-25 14:04 ` Lu, Wenzhuo
2017-07-31 12:06 ` 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=2f01d8a2-a484-6d8b-43c3-41f011a9c8ac@intel.com \
--to=ferruh.yigit@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=kubax.kozak@intel.com \
--cc=michalx.k.jastrzebski@intel.com \
--cc=stable@dpdk.org \
--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).