DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Cc: dev@dpdk.org, declan.doherty@intel.com, arkadiuszx.kusztal@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/test: fix array overflow warning with gcc 4.5
Date: Mon, 13 Jun 2016 22:04:18 +0200	[thread overview]
Message-ID: <4121599.adsh2vQa8a@xps13> (raw)
In-Reply-To: <1465470872-2652-1-git-send-email-tomaszx.kulasek@intel.com>

2016-06-09 13:14, Tomasz Kulasek:
> DPDK/app/test/test_cryptodev.c: In function ‘create_snow3g_cipher_operation
> _oop.clone.15’: DPDK/x86_64-native-linuxapp-gcc/include/rte_memcpy.h:796:14
> error: array subscript is above array bounds.
> 
> In test_cryptodev.c:
> 2429	rte_memcpy(sym_op->cipher.iv.data, iv, iv_len);
> 
> When iv_len is declared as 'unsigned int', rte_memcpy evaluates code for
> buffer size bigger than 255, but while 'iv' array is 64 bytes long, it
> causes 'above array bounds' warning in gcc 4.5 and breaks compilation.
> 
> Using uint8_t as a size of copied block prevents to evaluate in rte_memcpy
> code for length bigger than 255, causing the problem.
> 
> The root of this issue and solution is the same as for commit 2c007ea10616
> ("app/test: fix array overflow warning with gcc 4.5")
> 
> Fixes: 9727af14b032 ("app/test: add out-of-place symmetric crypto
>        operations")
> 
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>

Applied, thanks

      reply	other threads:[~2016-06-13 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 11:14 Tomasz Kulasek
2016-06-13 20:04 ` 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=4121599.adsh2vQa8a@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=tomaszx.kulasek@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).