On Tue, Jul 29, 2025 at 10:54 AM kernel test robot <lkp@xxxxxxxxx> wrote: > > Hi Sami, > > kernel test robot noticed the following build warnings: > > [auto build test WARNING on 5b4c54ac49af7f486806d79e3233fc8a9363961c] > > url: https://github.com/intel-lab-lkp/linux/commits/Sami-Tolvanen/bpf-crypto-Use-the-correct-destructor-kfunc-type/20250729-042936 > base: 5b4c54ac49af7f486806d79e3233fc8a9363961c > patch link: https://lore.kernel.org/r/20250728202656.559071-7-samitolvanen%40google.com > patch subject: [PATCH bpf-next v3 1/4] bpf: crypto: Use the correct destructor kfunc type > config: alpha-randconfig-r111-20250729 (https://download.01.org/0day-ci/archive/20250730/202507300122.RpqIKqFR-lkp@xxxxxxxxx/config) > compiler: alpha-linux-gcc (GCC) 8.5.0 > reproduce: (https://download.01.org/0day-ci/archive/20250730/202507300122.RpqIKqFR-lkp@xxxxxxxxx/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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202507300122.RpqIKqFR-lkp@xxxxxxxxx/ > > 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 __bpf_kfunc_start_defs() disables -Wmissing-declarations here, but I assume sparse doesn't care about that. Is there something we can do to teach it about this? Sami
