From: "D. Wythe" <alibuda@linux.alibaba.com>
To: kernel test robot <lkp@intel.com>,
kgraul@linux.ibm.com, wenjia@linux.ibm.com, jaka@linux.ibm.com,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, linux-rdma@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 1/2] net/smc: Introduce BPF injection capability for SMC
Date: Tue, 21 Feb 2023 19:55:46 +0800 [thread overview]
Message-ID: <7ff5ad40-7280-2060-4402-d3bada4ce200@linux.alibaba.com> (raw)
In-Reply-To: <202302211908.BgagxpRo-lkp@intel.com>
Thanks! I will repost a fixed patch.
On 2/21/23 7:30 PM, kernel test robot wrote:
> Hi Wythe,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on bpf-next/master]
>
> url: https://github.com/intel-lab-lkp/linux/commits/D-Wythe/net-smc-Introduce-BPF-injection-capability-for-SMC/20230221-155712
> base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
> patch link: https://lore.kernel.org/r/1676966191-47736-2-git-send-email-alibuda%40linux.alibaba.com
> patch subject: [PATCH bpf-next 1/2] net/smc: Introduce BPF injection capability for SMC
> config: i386-randconfig-a013-20230220 (https://download.01.org/0day-ci/archive/20230221/202302211908.BgagxpRo-lkp@intel.com/config)
> compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
> 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://github.com/intel-lab-lkp/linux/commit/e2b31aece49068d7a07ca4bbd5fbdbd92f45a25e
> git remote add linux-review https://github.com/intel-lab-lkp/linux
> git fetch --no-tags linux-review D-Wythe/net-smc-Introduce-BPF-injection-capability-for-SMC/20230221-155712
> git checkout e2b31aece49068d7a07ca4bbd5fbdbd92f45a25e
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash net/
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202302211908.BgagxpRo-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> net/smc/bpf_smc_struct_ops.c:61:33: error: use of undeclared identifier 'BTF_SMC_TYPE_MAX'; did you mean 'BTF_SMC_TYPE_SOCK'?
> BTF_ID_LIST_GLOBAL(btf_smc_ids, BTF_SMC_TYPE_MAX)
> ^~~~~~~~~~~~~~~~
> BTF_SMC_TYPE_SOCK
> include/linux/btf_ids.h:211:61: note: expanded from macro 'BTF_ID_LIST_GLOBAL'
> #define BTF_ID_LIST_GLOBAL(name, n) u32 __maybe_unused name[n];
> ^
> include/linux/btf_ids.h:275:1: note: 'BTF_SMC_TYPE_SOCK' declared here
> BTF_SMC_TYPE_xxx
> ^
> include/linux/btf_ids.h:269:15: note: expanded from macro 'BTF_SMC_TYPE_xxx'
> BTF_SMC_TYPE(BTF_SMC_TYPE_SOCK, smc_sock) \
> ^
> 1 error generated.
>
>
> vim +61 net/smc/bpf_smc_struct_ops.c
>
> 59
> 60 /* define global smc ID for smc_struct_ops */
> > 61 BTF_ID_LIST_GLOBAL(btf_smc_ids, BTF_SMC_TYPE_MAX)
> 62 #define BTF_SMC_TYPE(name, type) BTF_ID(struct, type)
> 63 BTF_SMC_TYPE_xxx
> 64 #undef BTF_SMC_TYPE
> 65
>
next prev parent reply other threads:[~2023-02-21 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 7:56 [PATCH bpf-next 0/2] net/smc: Introduce BPF injection capability D. Wythe
2023-02-21 7:56 ` [PATCH bpf-next 1/2] net/smc: Introduce BPF injection capability for SMC D. Wythe
2023-02-21 11:30 ` kernel test robot
2023-02-21 11:55 ` D. Wythe [this message]
2023-02-21 13:01 ` kernel test robot
2023-02-21 7:56 ` [PATCH bpf-next 2/2] bpf/selftests: Test for SMC protocol negotiate D. Wythe
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=7ff5ad40-7280-2060-4402-d3bada4ce200@linux.alibaba.com \
--to=alibuda@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wenjia@linux.ibm.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