From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
Cc: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] examples/l2fwd-crypto: out-of-bounds read
Date: Mon, 11 Jul 2016 16:50:48 +0200 [thread overview]
Message-ID: <3643994.5KeFe9M07i@xps13> (raw)
In-Reply-To: <ded3b9e5-d7d0-de76-0bd4-99a265391661@intel.com>
> > Overrunning array crypto_statistics of 32 64-byte elements
> > at element index 63 using index cdevid.
> > Fixed by extend crypto_statistics array.
> >
> > Fixes: 387259bd6c67 ("examples/l2fwd-crypto: add sample application")
> > Coverity ID 120145
> >
> > Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> >
> Acked-by: Declan Doherty <declan.doherty@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-07-11 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 12:19 Slawomir Mrozowicz
2016-06-30 9:15 ` Declan Doherty
2016-07-11 14:50 ` Thomas Monjalon [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=3643994.5KeFe9M07i@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).