From: kernel test robot <lkp@intel.com>
To: linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Daniel Hodges <git@danielhodges.dev>
Subject: Re: [PATCH bpf-next 3/4] bpf: Add ECDSA signature verification kfuncs
Date: Wed, 19 Nov 2025 01:28:27 +0800 [thread overview]
Message-ID: <202511190147.y9V59VgY-lkp@intel.com> (raw)
In-Reply-To: <20251117211413.1394-4-git@danielhodges.dev>
Hi Daniel,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bpf-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Daniel-Hodges/bpf-Add-SHA-hash-kfuncs-for-cryptographic-hashing/20251118-051958
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/r/20251117211413.1394-4-git%40danielhodges.dev
patch subject: [PATCH bpf-next 3/4] bpf: Add ECDSA signature verification kfuncs
config: openrisc-randconfig-r133-20251118 (https://download.01.org/0day-ci/archive/20251119/202511190147.y9V59VgY-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251119/202511190147.y9V59VgY-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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511190147.y9V59VgY-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/bpf/crypto.c:607:34: sparse: sparse: symbol 'bpf_ecdsa_ctx_acquire' was not declared. Should it be static?
vim +/bpf_ecdsa_ctx_acquire +607 kernel/bpf/crypto.c
606
> 607 __bpf_kfunc struct bpf_ecdsa_ctx *
608 bpf_ecdsa_ctx_acquire(struct bpf_ecdsa_ctx *ctx)
609 {
610 if (!refcount_inc_not_zero(&ctx->usage))
611 return NULL;
612 return ctx;
613 }
614
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-11-18 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251117211413.1394-1-git@danielhodges.dev>
2025-11-17 21:13 ` [PATCH bpf-next 1/4] bpf: Add SHA hash kfuncs for cryptographic hashing Daniel Hodges
2025-11-18 10:11 ` kernel test robot
2025-11-18 12:13 ` Vadim Fedorenko
2025-11-18 15:53 ` kernel test robot
2025-11-17 21:13 ` [PATCH bpf-next 2/4] selftests/bpf: Add tests for SHA hash kfuncs Daniel Hodges
2025-11-18 13:45 ` Vadim Fedorenko
2025-11-17 21:14 ` [PATCH bpf-next 3/4] bpf: Add ECDSA signature verification kfuncs Daniel Hodges
2025-11-18 17:28 ` kernel test robot [this message]
2025-11-17 21:14 ` [PATCH bpf-next 4/4] selftests/bpf: Add tests for " Daniel Hodges
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=202511190147.y9V59VgY-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@danielhodges.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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