From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>,
Kenta Shinohara <shinohara.kenta@lab.ntt.co.jp>,
spp@dpdk.org
Subject: Re: [spp] [PATCH] spp_vf: change char length to avoid compile error
Date: Thu, 3 May 2018 16:53:25 +0100 [thread overview]
Message-ID: <071d00d3-3f7c-1cd9-92e7-b84f30040ff0@intel.com> (raw)
In-Reply-To: <e94905a7-0f98-24ea-4b79-fed79d5e905b@lab.ntt.co.jp>
On 4/16/2018 7:07 AM, Yasufumi Ogawa wrote:
> On 2018/04/16 11:26, Kenta Shinohara wrote:
>> Change character length of SPP_CMD_VALUE_BUFSZ to avoid compile error
>> on gcc-7.
>>
>> Signed-off-by: Kenta Shinohara <shinohara.kenta@lab.ntt.co.jp>
> Hi Kenta,
>
> Thank you for your contribution!
>
> I also tried to compile met the same problem on Ubuntu 17.10 and gcc ver 7.1. It seems that checking is more strict in gcc ver
> 7.1 while ver 5.4 on Ubuntu 16.04 LTS. Your patch is working on both of Ubuntu16.04 and 17.10.
>
> spp/src/vf/command_proc.c:231:37: error: ‘%s’ directive writing up to 127 bytes into a region of size 112 [-Werror=format-overflow=]
> sprintf(message, "unknown command(%s)", decode_error->value);
> ^~ ~~~~~~~~~~~~
> In file included from /usr/include/stdio.h:862:0,
> from /home/ubuntu/dpdk-home/dpdk/x86_64-native-linuxapp-gcc/include/rte_log.h:50,
> from /home/ubuntu/dpdk-home/spp/src/vf/command_proc.c:4:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___sprintf_chk’ output between 18 and 145 bytes into a
> destination of size 128
> return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> __bos (__s), __fmt, __va_arg_pack ());
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> I think it is acceptable to change buf size from 128 to 111 because command is not so long to exceed over 100 chars in spp_vf.
>
> Acked-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Applied, thanks.
(The build error and comment to change buf size to 111 added to commit log)
prev parent reply other threads:[~2018-05-03 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 2:26 Kenta Shinohara
2018-04-16 6:07 ` Yasufumi Ogawa
2018-05-03 15:53 ` Ferruh Yigit [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=071d00d3-3f7c-1cd9-92e7-b84f30040ff0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=shinohara.kenta@lab.ntt.co.jp \
--cc=spp@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).