All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Patch bpf-next v2 4/5] skmsg: use skb ext instead of TCP_SKB_CB
Date: Wed, 10 Feb 2021 23:30:15 +0800	[thread overview]
Message-ID: <202102102357.LamqPWnP-lkp@intel.com> (raw)
In-Reply-To: <20210210022136.146528-5-xiyou.wangcong@gmail.com>

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

Hi Cong,

I love your patch! Yet something to improve:

[auto build test ERROR on bpf-next/master]

url:    https://github.com/0day-ci/linux/commits/Cong-Wang/sock_map-clean-up-and-refactor-code-for-BPF_SK_SKB_VERDICT/20210210-103313
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
config: arm64-randconfig-r016-20210209 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project c9439ca36342fb6013187d0a69aef92736951476)
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
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/db0537152e20e7b3606cb5c5d6938077c78b9341
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Cong-Wang/sock_map-clean-up-and-refactor-code-for-BPF_SK_SKB_VERDICT/20210210-103313
        git checkout db0537152e20e7b3606cb5c5d6938077c78b9341
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64 

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 kernel/bpf/btf.c:22:
>> include/linux/skmsg.h:466:28: error: implicit declaration of function 'skb_ext_find' [-Werror,-Wimplicit-function-declaration]
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                     ^
>> include/linux/skmsg.h:466:46: error: use of undeclared identifier 'SKB_EXT_BPF'
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                                       ^
   include/linux/skmsg.h:474:28: error: implicit declaration of function 'skb_ext_find' [-Werror,-Wimplicit-function-declaration]
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                     ^
   include/linux/skmsg.h:474:46: error: use of undeclared identifier 'SKB_EXT_BPF'
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                                       ^
   include/linux/skmsg.h:482:28: error: implicit declaration of function 'skb_ext_find' [-Werror,-Wimplicit-function-declaration]
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                     ^
   include/linux/skmsg.h:482:46: error: use of undeclared identifier 'SKB_EXT_BPF'
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                                       ^
   include/linux/skmsg.h:490:28: error: implicit declaration of function 'skb_ext_find' [-Werror,-Wimplicit-function-declaration]
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                     ^
   include/linux/skmsg.h:490:46: error: use of undeclared identifier 'SKB_EXT_BPF'
           struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
                                                       ^
   8 errors generated.

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for NET_SOCK_MSG
   Depends on NET
   Selected by
   - BPF_SYSCALL


vim +/skb_ext_find +466 include/linux/skmsg.h

   461	
   462	#if IS_ENABLED(CONFIG_NET_SOCK_MSG)
   463	static inline
   464	bool skb_bpf_ext_ingress(const struct sk_buff *skb)
   465	{
 > 466		struct skb_bpf_ext *ext = skb_ext_find(skb, SKB_EXT_BPF);
   467	
   468		return ext->flags & BPF_F_INGRESS;
   469	}
   470	

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

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

  reply	other threads:[~2021-02-10 15:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  2:21 [Patch bpf-next v2 0/5] sock_map: clean up and refactor code for BPF_SK_SKB_VERDICT Cong Wang
2021-02-10  2:21 ` [Patch bpf-next v2 1/5] bpf: clean up sockmap related Kconfigs Cong Wang
2021-02-10 10:05   ` kernel test robot
2021-02-10 12:56   ` kernel test robot
2021-02-10  2:21 ` [Patch bpf-next v2 2/5] skmsg: get rid of struct sk_psock_parser Cong Wang
2021-02-12 10:56   ` Lorenz Bauer
2021-02-12 19:09     ` Cong Wang
2021-02-13  1:58       ` Cong Wang
2021-02-10  2:21 ` [Patch bpf-next v2 3/5] bpf: compute data_end dynamically with JIT code Cong Wang
2021-02-12 10:55   ` Lorenz Bauer
2021-02-12 19:01     ` Cong Wang
2021-02-10  2:21 ` [Patch bpf-next v2 4/5] skmsg: use skb ext instead of TCP_SKB_CB Cong Wang
2021-02-10 15:30   ` kernel test robot [this message]
2021-02-12 10:58   ` Lorenz Bauer
2021-02-10  2:21 ` [Patch bpf-next v2 5/5] sock_map: rename skb_parser and skb_verdict Cong Wang
2021-02-12 10:59   ` Lorenz Bauer

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=202102102357.LamqPWnP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.