From: Thomas Monjalon <thomas@monjalon.net>
To: "Xu, Rosen" <rosen.xu@intel.com>, "Pei, Andy" <andy.pei@intel.com>
Cc: stable@dpdk.org, qabuild <qabuild@intel.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>
Subject: Re: [dpdk-stable] [DPDK] raw/ifpga: fix unintentional integer overflow
Date: Thu, 04 Jul 2019 15:53:34 +0200 [thread overview]
Message-ID: <40059125.hhW5lyQpyE@xps> (raw)
In-Reply-To: <0E78D399C70DA940A335608C6ED296D73A76E9FA@SHSMSX104.ccr.corp.intel.com>
> > cast unsigned int ports_per_retimer, unsigned int nums_retimer, unsigned
> > int nums_fvl and unsigned int ports_per_fvl to uint64_t before multiply
> > operation, to avoid Unintentional integer overflow.
> >
> > Coverity issue: 337924, 337926
> > Fixes: d1cd4eb2d48e ("raw/ifpga: support ipn3ke")
> > Cc: rosen.xu@intel.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Andy Pei <andy.pei@intel.com>
>
> Acked-by: Rosen Xu <rosen.xu@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-07-04 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 6:36 Andy Pei
2019-05-23 2:08 ` Xu, Rosen
2019-07-04 13:53 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-22 2:59 Andy Pei
2019-05-23 2:58 ` Xu, Rosen
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=40059125.hhW5lyQpyE@xps \
--to=thomas@monjalon.net \
--cc=andy.pei@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=qabuild@intel.com \
--cc=rosen.xu@intel.com \
--cc=stable@dpdk.org \
/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).