DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Markos Chandras <mchandras@suse.de>, Nirmoy Das <ndas@suse.de>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: disable new gcc truncation flag
Date: Tue, 13 Jun 2017 17:50:04 +0100	[thread overview]
Message-ID: <63166491-52c0-57f5-2a3b-f28d62d702ac@intel.com> (raw)
In-Reply-To: <39f781d5-935d-8ada-2922-9803216b3f59@suse.de>

On 6/13/2017 2:49 PM, Markos Chandras wrote:
> On 06/13/2017 04:45 PM, Ferruh Yigit wrote:
>> On 6/13/2017 10:18 AM, Nirmoy Das wrote:
>>>
>>>
>>> On 06/12/2017 04:35 PM, Markos Chandras wrote:
>>>> On 06/02/2017 07:38 PM, Markos Chandras wrote:
>>>>> On 06/02/2017 05:31 PM, Nirmoy Das wrote:
>>>>>> disable truncation check to ignore below warning
>>>>>> dpdk/x86_64-native-linuxapp-gcc-default/build/lib/librte_eal/linuxapp/kni/igb_main.c:2476:30: error: '%d' directive output may be truncated writing between 1 and 5 bytes into a region of size between 0 and 11 [-Werror=format-truncation=]
>>>>>>
>>>>>> Signed-off-by: Nirmoy Das <ndas@suse.de>
>>>>>> ---
>>>>> I haven't check the code but is this a bogus warning or a real one? If
>>>>> it's bogus then could you explain why in the commit message so we do not
>>>>> bring it back in the future? If it's a real problem, then perhaps worth
>>>>> fixing it instead of masking it?
>>>>>
>>>> Actually this should have already been fixed in the series posted in
>>>> http://dpdk.org/ml/archives/dev/2017-May/065261.html
>>> I see the issue in master with CONFIG_RTE_KNI_KMOD_ETHTOOL=y
>>
>> I confirm the build error, and patch fixes it.
>>
>> Although that piece of code most probably will not be used at all, and
>> previous solution was to disable warnings, since this warning is only
>> single place in KNI code, it is easy to fix and I am for fixing it [1],
>> what do you think?
>>
>>
>> diff --git a/lib/librte_eal/linuxapp/kni/ethtool/igb/igb.h
>> b/lib/librte_eal/linuxapp/kni/ethtool/igb/igb.h
>> index d077b49e9..8667f29ca 100644
>> --- a/lib/librte_eal/linuxapp/kni/ethtool/igb/igb.h
>> +++ b/lib/librte_eal/linuxapp/kni/ethtool/igb/igb.h
>> @@ -607,7 +607,7 @@ struct igb_adapter {
>>         int int_mode;
>>         u32 rss_queues;
>>         u32 vmdq_pools;
>> -       char fw_version[32];
>> +       char fw_version[43];
>>         u32 wvbr;
>>         struct igb_mac_addr *mac_table;
>>  #ifdef CONFIG_IGB_VMDQ_NETDEV
>>
> 
> Looks reasonable to me

Sent http://dpdk.org/dev/patchwork/patch/25297/

      reply	other threads:[~2017-06-13 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02 16:31 Nirmoy Das
2017-06-02 16:38 ` Markos Chandras
2017-06-12 14:35   ` Markos Chandras
2017-06-13  9:18     ` Nirmoy Das
2017-06-13 10:01       ` Markos Chandras
2017-06-13 13:45       ` Ferruh Yigit
2017-06-13 13:49         ` Markos Chandras
2017-06-13 16:50           ` 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=63166491-52c0-57f5-2a3b-f28d62d702ac@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=mchandras@suse.de \
    --cc=ndas@suse.de \
    /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).