From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Qiao, Wenjing" <wenjing.qiao@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Zhang, Yuying" <yuying.zhang@intel.com>
Subject: RE: [PATCH] net/cpfl: fix coverity issues
Date: Tue, 7 Nov 2023 00:18:42 +0000 [thread overview]
Message-ID: <DM4PR11MB599405C1F78C5BDAED1402F9D7A9A@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231106095933.962565-1-wenjing.qiao@intel.com>
> -----Original Message-----
> From: Qiao, Wenjing <wenjing.qiao@intel.com>
> Sent: Monday, November 6, 2023 6:00 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Zhang, Yuying <yuying.zhang@intel.com>; Qiao, Wenjing
> <wenjing.qiao@intel.com>
> Subject: [PATCH] net/cpfl: fix coverity issues
>
> From: Wenjing Qiao <wenjing.qiao@intel.com>
>
> Fix integer handling issues, tainted_scalar issues, uninit issues, overrun issues
> and control flow issues reported by coverity scan.
>
> Coverity issue: 403259
> Coverity issue: 403261
> Coverity issue: 403266
> Coverity issue: 403267
> Coverity issue: 403271
> Coverity issue: 403274
> Fixes: db042ef09d26 ("net/cpfl: implement FXP rule creation and destroying")
> Fixes: 03f976012304 ("net/cpfl: adapt FXP to flow engine")
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2023-11-07 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 9:59 wenjing.qiao
2023-11-07 0:18 ` Zhang, Qi Z [this message]
2023-11-12 17:42 ` Thomas Monjalon
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=DM4PR11MB599405C1F78C5BDAED1402F9D7A9A@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=wenjing.qiao@intel.com \
--cc=yuying.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).