linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [linux-next:master 7868/8410] net/netfilter/core.c:353:20: error: unused function 'nf_egress_hook'
Date: Sat, 16 Oct 2021 06:12:41 +0800	[thread overview]
Message-ID: <202110160632.WzahPgao-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   7c832d2f9b959e3181370c8b0dacaf9efe13fc05
commit: 42df6e1d221dddc0f2acf2be37e68d553ad65f96 [7868/8410] netfilter: Introduce egress hook
config: x86_64-buildonly-randconfig-r003-20211015 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 6069a6a5049497a32a50a49661c2f4169078bdba)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=42df6e1d221dddc0f2acf2be37e68d553ad65f96
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 42df6e1d221dddc0f2acf2be37e68d553ad65f96
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64 

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 >>):

   net/netfilter/core.c:344:20: error: unused function 'nf_ingress_hook' [-Werror,-Wunused-function]
   static inline bool nf_ingress_hook(const struct nf_hook_ops *reg, int pf)
                      ^
>> net/netfilter/core.c:353:20: error: unused function 'nf_egress_hook' [-Werror,-Wunused-function]
   static inline bool nf_egress_hook(const struct nf_hook_ops *reg, int pf)
                      ^
   2 errors generated.


vim +/nf_egress_hook +353 net/netfilter/core.c

   343	
 > 344	static inline bool nf_ingress_hook(const struct nf_hook_ops *reg, int pf)
   345	{
   346		if ((pf == NFPROTO_NETDEV && reg->hooknum == NF_NETDEV_INGRESS) ||
   347		    (pf == NFPROTO_INET && reg->hooknum == NF_INET_INGRESS))
   348			return true;
   349	
   350		return false;
   351	}
   352	
 > 353	static inline bool nf_egress_hook(const struct nf_hook_ops *reg, int pf)
   354	{
   355		return pf == NFPROTO_NETDEV && reg->hooknum == NF_NETDEV_EGRESS;
   356	}
   357	

---
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: 45907 bytes --]

             reply	other threads:[~2021-10-15 22:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 22:12 kernel test robot [this message]
2021-10-16  8:13 ` [PATCH nf-next] netfilter: core: Fix clang warnings about unused static inlines Lukas Wunner
2021-10-17 13:48   ` Pablo Neira Ayuso

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=202110160632.WzahPgao-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=lukas@wunner.de \
    --cc=pablo@netfilter.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).