Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Salil Mehta <salil.mehta@huawei.com>
Cc: kbuild-all@01.org, davem@davemloft.net, salil.mehta@huawei.com,
	yisen.zhuang@huawei.com, mehta.salil.lnk@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com
Subject: Re: [PATCH V3 net-next] net: hns: Fix to conditionally convey RX checksum flag to stack
Date: Tue, 6 Dec 2016 04:11:56 +0800	[thread overview]
Message-ID: <201612060439.qL730ViZ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20161205153757.386156-1-salil.mehta@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]

Hi Salil,

[auto build test WARNING on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Salil-Mehta/net-hns-Fix-to-conditionally-convey-RX-checksum-flag-to-stack/20161206-022948
config: i386-allmodconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings

All warnings (new ones prefixed by >>):

   drivers/net/ethernet/hisilicon/hns/hns_enet.c: In function 'hns_nic_rx_poll_one':
>> drivers/net/ethernet/hisilicon/hns/hns_enet.c:606:5: warning: 'l3id' may be used uninitialized in this function [-Wmaybe-uninitialized]
     if ((l3id != HNS_RX_FLAG_L3ID_IPV4) && (l3id != HNS_RX_FLAG_L3ID_IPV6))
        ^
   drivers/net/ethernet/hisilicon/hns/hns_enet.c:573:6: note: 'l3id' was declared here
     u32 l3id;
         ^~~~
>> drivers/net/ethernet/hisilicon/hns/hns_enet.c:618:37: warning: 'l4id' may be used uninitialized in this function [-Wmaybe-uninitialized]
     if ((l4id != HNS_RX_FLAG_L4ID_TCP) &&
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
         (l4id != HNS_RX_FLAG_L4ID_UDP) &&
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~  
   drivers/net/ethernet/hisilicon/hns/hns_enet.c:574:6: note: 'l4id' was declared here
     u32 l4id;
         ^~~~

vim +/l3id +606 drivers/net/ethernet/hisilicon/hns/hns_enet.c

   600		 * checksum or any other L3/L4 error, we will not (cannot) convey
   601		 * checksum status for such cases to upper stack and will not maintain
   602		 * the RX L3/L4 checksum counters as well.
   603		 */
   604	
   605		/*  check L3 protocol for which checksum is supported */
 > 606		if ((l3id != HNS_RX_FLAG_L3ID_IPV4) && (l3id != HNS_RX_FLAG_L3ID_IPV6))
   607			return;
   608	
   609		/* check for any(not just checksum)flagged L3 protocol errors */
   610		if (unlikely(hnae_get_bit(flag, HNS_RXD_L3E_B)))
   611			return;
   612	
   613		/* we do not support checksum of fragmented packets */
   614		if (unlikely(hnae_get_bit(flag, HNS_RXD_FRAG_B)))
   615			return;
   616	
   617		/*  check L4 protocol for which checksum is supported */
 > 618		if ((l4id != HNS_RX_FLAG_L4ID_TCP) &&
   619		    (l4id != HNS_RX_FLAG_L4ID_UDP) &&
   620		    (l4id != HNS_RX_FLAG_L4ID_SCTP))
   621			return;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 57010 bytes --]

      reply	other threads:[~2016-12-05 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 15:37 [PATCH V3 net-next] net: hns: Fix to conditionally convey RX checksum flag to stack Salil Mehta
2016-12-05 20:11 ` kbuild test robot [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=201612060439.qL730ViZ%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=mehta.salil.lnk@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=salil.mehta@huawei.com \
    --cc=yisen.zhuang@huawei.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