public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel•com>
To: Heng Guo <heng.guo@windriver•com>,
	davem@davemloft•net, sahern@kernel•org, edumazet@google•com,
	kuba@kernel•org, pabeni@redhat•com
Cc: oe-kbuild-all@lists•linux.dev, netdev@vger•kernel.org,
	filip.pudak@windriver•com, heng.guo@windriver•com
Subject: Re: [PATCH 1/1] net: ipv4,ipv6: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check
Date: Thu, 14 Sep 2023 17:34:28 +0800	[thread overview]
Message-ID: <202309141701.7OFxGdE5-lkp@intel.com> (raw)
In-Reply-To: <20230914051623.2180843-2-heng.guo@windriver.com>

Hi Heng,

kernel test robot noticed the following build warnings:

[auto build test WARNING on net-next/main]
[also build test WARNING on net/main linus/master v6.6-rc1 next-20230914]
[cannot apply to horms-ipvs/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Heng-Guo/net-ipv4-ipv6-fix-IPSTATS_MIB_OUTFORWDATAGRAMS-increment-after-fragment-check/20230914-131757
base:   net-next/main
patch link:    https://lore.kernel.org/r/20230914051623.2180843-2-heng.guo%40windriver.com
patch subject: [PATCH 1/1] net: ipv4,ipv6: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20230914/202309141701.7OFxGdE5-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230914/202309141701.7OFxGdE5-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel•com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309141701.7OFxGdE5-lkp@intel.com/

All warnings (new ones prefixed by >>):

   net/ipv6/ip6_output.c: In function 'ip6_forward_finish':
>> net/ipv6/ip6_output.c:451:27: warning: unused variable 'dst' [-Wunused-variable]
     451 |         struct dst_entry *dst = skb_dst(skb);
         |                           ^~~


vim +/dst +451 net/ipv6/ip6_output.c

e21e0b5f19ac78 Ville Nuorvala    2006-09-22  447  
0c4b51f0054ce8 Eric W. Biederman 2015-09-15  448  static inline int ip6_forward_finish(struct net *net, struct sock *sk,
0c4b51f0054ce8 Eric W. Biederman 2015-09-15  449  				     struct sk_buff *skb)
^1da177e4c3f41 Linus Torvalds    2005-04-16  450  {
71a1c915238c97 Jeff Barnhill     2018-04-05 @451  	struct dst_entry *dst = skb_dst(skb);
71a1c915238c97 Jeff Barnhill     2018-04-05  452  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-09-14  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  5:16 [PATCH 0/1] Issue description and debug Heng Guo
2023-09-14  5:16 ` [PATCH 1/1] net: ipv4,ipv6: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check Heng Guo
2023-09-14  9:34   ` kernel test robot [this message]
2023-09-19  9:38   ` [PATCH v2 0/1] Issue description and debug Heng Guo
2023-09-19  9:38     ` [PATCH v2] net: ipv4,ipv6: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check Heng Guo
2023-09-21  7:46       ` Paolo Abeni
2023-09-21  9:23   ` [PATCH v3 0/1] Issue description and debug Heng Guo
2023-09-21  9:23     ` [PATCH v3 1/1] net-next: fix IPSTATS_MIB_OUTFORWDATAGRAMS increment after fragment check Heng Guo
2023-09-28  2:11       ` heng guo
2023-10-02 19:32         ` Jakub Kicinski

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=202309141701.7OFxGdE5-lkp@intel.com \
    --to=lkp@intel$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=filip.pudak@windriver$(echo .)com \
    --cc=heng.guo@windriver$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=oe-kbuild-all@lists$(echo .)linux.dev \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sahern@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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