netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Ryoga Saito <contact@proelbtn.com>, netfilter-devel@vger.kernel.org
Cc: kbuild-all@lists.01.org, pablo@netfilter.org,
	stefano.salsano@uniroma2.it, andrea.mayer@uniroma2.it,
	davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
	dsahern@kernel.org, Ryoga Saito <contact@proelbtn.com>
Subject: Re: [PATCH v3 1/2] netfilter: add new sysctl toggle for lightweight tunnel netfilter hooks
Date: Sat, 31 Jul 2021 04:21:48 +0800	[thread overview]
Message-ID: <202107310413.DlMT6tps-lkp@intel.com> (raw)
In-Reply-To: <7369c6af9a8190f08ede4e936b505b6eedc871a6.1627571302.git.contact@proelbtn.com>

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

Hi Ryoga,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on nf-next/master]
[also build test ERROR on nf/master ipvs/master linus/master v5.14-rc3 next-20210730]
[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]

url:    https://github.com/0day-ci/linux/commits/Ryoga-Saito/netfilter-add-new-sysctl-toggle-for-lightweight-tunnel-netfilter-hooks/20210730-002403
base:   https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
config: x86_64-defconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/c406e7bc7831acf318fd8217b94d2d9bc1f62deb
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Ryoga-Saito/netfilter-add-new-sysctl-toggle-for-lightweight-tunnel-netfilter-hooks/20210730-002403
        git checkout c406e7bc7831acf318fd8217b94d2d9bc1f62deb
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/linux/static_key.h:1,
                    from arch/x86/include/asm/nospec-branch.h:6,
                    from arch/x86/include/asm/irqflags.h:9,
                    from include/linux/irqflags.h:16,
                    from include/linux/rcupdate.h:26,
                    from include/linux/sysctl.h:26,
                    from net/netfilter/nf_conntrack_lwtunnel.c:3:
   net/netfilter/nf_conntrack_lwtunnel.c: In function 'nf_conntrack_lwtunnel_get':
>> net/netfilter/nf_conntrack_lwtunnel.c:9:30: error: 'nf_ct_lwtunnel_enabled' undeclared (first use in this function)
       9 |  if (static_branch_unlikely(&nf_ct_lwtunnel_enabled))
         |                              ^~~~~~~~~~~~~~~~~~~~~~
   include/linux/jump_label.h:484:43: note: in definition of macro 'static_branch_unlikely'
     484 |  if (__builtin_types_compatible_p(typeof(*x), struct static_key_true)) \
         |                                           ^
   net/netfilter/nf_conntrack_lwtunnel.c:9:30: note: each undeclared identifier is reported only once for each function it appears in
       9 |  if (static_branch_unlikely(&nf_ct_lwtunnel_enabled))
         |                              ^~~~~~~~~~~~~~~~~~~~~~
   include/linux/jump_label.h:484:43: note: in definition of macro 'static_branch_unlikely'
     484 |  if (__builtin_types_compatible_p(typeof(*x), struct static_key_true)) \
         |                                           ^
   net/netfilter/nf_conntrack_lwtunnel.c: In function 'nf_conntrack_lwtunnel_set':
   net/netfilter/nf_conntrack_lwtunnel.c:17:30: error: 'nf_ct_lwtunnel_enabled' undeclared (first use in this function)
      17 |  if (static_branch_unlikely(&nf_ct_lwtunnel_enabled)) {
         |                              ^~~~~~~~~~~~~~~~~~~~~~
   include/linux/jump_label.h:484:43: note: in definition of macro 'static_branch_unlikely'
     484 |  if (__builtin_types_compatible_p(typeof(*x), struct static_key_true)) \
         |                                           ^


vim +/nf_ct_lwtunnel_enabled +9 net/netfilter/nf_conntrack_lwtunnel.c

     6	
     7	static inline int nf_conntrack_lwtunnel_get(void)
     8	{
   > 9		if (static_branch_unlikely(&nf_ct_lwtunnel_enabled))
    10			return 1;
    11		else
    12			return 0;
    13	}
    14	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  reply	other threads:[~2021-07-30 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29 15:22 [PATCH v3 0/2] netfilter: add netfilter hooks to track SRv6-encapsulated flows Ryoga Saito
2021-07-29 15:22 ` [PATCH v3 1/2] netfilter: add new sysctl toggle for lightweight tunnel netfilter hooks Ryoga Saito
2021-07-30 20:21   ` kernel test robot [this message]
2021-07-29 15:22 ` [PATCH v3 2/2] netfilter: add netfilter hooks to SRv6 data plane Ryoga Saito

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=202107310413.DlMT6tps-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=contact@proelbtn.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=stefano.salsano@uniroma2.it \
    --cc=yoshfuji@linux-ipv6.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).