From: Ferruh Yigit <ferruh.yigit@intel.com>
To: SebastianX Basierski <sebastianx.basierski@intel.com>, skhare@vmware.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pmd_vmxnet3: Unintentional integer overflow
Date: Tue, 19 Sep 2017 15:44:36 +0100 [thread overview]
Message-ID: <178fb6b9-bd82-7f6e-5435-821035e6e0f5@intel.com> (raw)
In-Reply-To: <1505821678-33651-1-git-send-email-sebastianx.basierski@intel.com>
On 9/19/2017 12:47 PM, SebastianX Basierski wrote:
> Fixed overflow by casting txq->cmd_ring.next2fill to uint64_t type.
>
> Coverity issue: 143457
>
> Fixes: 01fef6e3c181 ("net/vmxnet3: allow variable length Tx data ring")
> Cc: skhare@vmware.com
> cc: dev@dpdk.org
>
> Signed-off-by: SebastianX Basierski <sebastianx.basierski@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2017-09-19 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 11:47 SebastianX Basierski
2017-09-19 14:44 ` Ferruh Yigit [this message]
2017-09-20 16:13 ` Ferruh Yigit
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=178fb6b9-bd82-7f6e-5435-821035e6e0f5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=sebastianx.basierski@intel.com \
--cc=skhare@vmware.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).