[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202601110205.4dwPV9eI-lkp@intel.com>
Date: Sun, 11 Jan 2026 02:49:17 +0800
From: kernel test robot <lkp@...el.com>
To: Sami Tolvanen <samitolvanen@...gle.com>, bpf@...r.kernel.org
Cc: oe-kbuild-all@...ts.linux.dev,
Vadim Fedorenko <vadim.fedorenko@...ux.dev>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Cong Wang <xiyou.wangcong@...il.com>, Jiri Pirko <jiri@...nulli.us>,
Viktor Malik <vmalik@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Sami Tolvanen <samitolvanen@...gle.com>
Subject: Re: [PATCH bpf-next v5 1/4] bpf: crypto: Use the correct destructor
kfunc type
Hi Sami,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 5714ca8cba5ed736f3733663c446cbee63a10a64]
url: https://github.com/intel-lab-lkp/linux/commits/Sami-Tolvanen/bpf-crypto-Use-the-correct-destructor-kfunc-type/20260110-162850
base: 5714ca8cba5ed736f3733663c446cbee63a10a64
patch link: https://lore.kernel.org/r/20260110082548.113748-7-samitolvanen%40google.com
patch subject: [PATCH bpf-next v5 1/4] bpf: crypto: Use the correct destructor kfunc type
config: sh-randconfig-r133-20260110 (https://download.01.org/0day-ci/archive/20260111/202601110205.4dwPV9eI-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260111/202601110205.4dwPV9eI-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601110205.4dwPV9eI-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/crypto.c:264:18: sparse: sparse: symbol 'bpf_crypto_ctx_release_dtor' was not declared. Should it be static?
vim +/bpf_crypto_ctx_release_dtor +264 kernel/bpf/crypto.c
263
> 264 __bpf_kfunc void bpf_crypto_ctx_release_dtor(void *ctx)
265 {
266 bpf_crypto_ctx_release(ctx);
267 }
268 CFI_NOSEAL(bpf_crypto_ctx_release_dtor);
269
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Powered by blists - more mailing lists