From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Zhang, Xiao" <xiao.zhang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Yang, Qiming" <qiming.yang@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [v2 0/5] fix dereference after null check coverity
Date: Tue, 6 Aug 2019 22:01:04 +0800 [thread overview]
Message-ID: <20190806140104.GA64886@intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E7061153D79AA2@SHSMSX105.ccr.corp.intel.com>
Hi, Xiao
On 08/06, Zhang, Qi Z wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ye Xiaolong
>> Sent: Monday, August 5, 2019 11:46 PM
>> To: Zhang, Xiao <xiao.zhang@intel.com>
>> Cc: dev@dpdk.org; Yang, Qiming <qiming.yang@intel.com>; Xing, Beilei
>> <beilei.xing@intel.com>; stable@dpdk.org
>> Subject: Re: [dpdk-dev] [v2 0/5] fix dereference after null check coverity
>>
>> On 08/06, Xiao Zhang wrote:
>> >This patch tries to fix (dereference after null check) coverity issue.
>> >The address of first segmented packets for ice, iavf, i40e fm10k and
>> >ixgbe was not set correctly during reassembling packets which led to this
>> issue.
>> >
>> >Coverity issue: 343452
>> >Coverity issue: 343407
>> >Fixes: c68a52b8 ("net/ice: support vector SSE in Rx") Coverity issue:
>> >343447
>> >Fixes: 319c421f ("net/avf: enable SSE Rx Tx") Coverity issue: 343422
>> >Coverity issue: 343403
>> >Fixes: ca74903b ("net/i40e: extract non-x86 specific code from vector
>> >driver") Coverity issue: 343416
>> >Fixes: fe65e1e1 ("fm10k: add vector scatter Rx") Coverity issue: 13245
>> >Fixes: 8a44c15a ("net/ixgbe: extract non-x86 specific code from vector
>> >driver")
>
>Fix tag size should be 12
You can add below alias section to you git config file to create proper fix tag conveniently.
[alias]
fixline = log -1 --abbrev=12 --format='Fixes: %h (\"%s\")%nCc: %ae'
Thanks,
Xiaolong
next prev parent reply other threads:[~2019-08-06 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 21:00 [dpdk-stable] [PATCH 1/5] net/fm10k: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-stable] [PATCH 2/5] net/iavf: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-stable] [PATCH 3/5] net/i40e: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-stable] [PATCH 4/5] net/ice: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-stable] [PATCH 5/5] net/ixgbe: " Xiao Zhang
2019-08-05 3:35 ` [dpdk-stable] [dpdk-dev] [PATCH 1/5] net/fm10k: " Ye Xiaolong
2019-08-05 23:20 ` [dpdk-stable] [v2 0/5] " Xiao Zhang
2019-08-05 15:46 ` Ye Xiaolong
2019-08-06 11:30 ` [dpdk-stable] [dpdk-dev] " Zhang, Qi Z
2019-08-06 14:01 ` Ye Xiaolong [this message]
2019-08-06 14:13 ` Zhang, Xiao
2019-08-05 23:20 ` [dpdk-stable] [PATCH v2 1/5] net/ixgbe: " Xiao Zhang
2019-08-05 23:20 ` [dpdk-stable] [PATCH v2 2/5] net/ice: " Xiao Zhang
2019-08-05 23:20 ` [dpdk-stable] [PATCH v2 3/5] net/i40e: " Xiao Zhang
2019-08-05 23:20 ` [dpdk-stable] [PATCH v2 4/5] net/iavf: " Xiao Zhang
2019-08-05 23:20 ` [dpdk-stable] [PATCH v2 5/5] net/fm10k: " Xiao Zhang
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=20190806140104.GA64886@intel.com \
--to=xiaolong.ye@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=xiao.zhang@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).