From: kernel test robot <lkp@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
keyrings@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
Jarkko Sakkinen <jarkko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Graf <tgraf@suug.ch>,
Herbert Xu <herbert@gondor.apana.org.au>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v3 5/6] KEYS: Replace assoc_array with rhashtable
Date: Wed, 28 Oct 2026 15:28:38 +0800 [thread overview]
Message-ID: <202610281546.OMDCubFW-lkp@intel.com> (raw)
In-Reply-To: <20261025001105.1824178-6-jarkko@kernel.org>
Hi Jarkko,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[cannot apply to akpm-mm/mm-nonmm-unstable manguebit/cifs-next manguebit/cifs-fixes device-mapper-dm/for-next fsverity/for-next fsverity/for-current shuah-kselftest/next shuah-kselftest/fixes dhowells-fs/fscache-next dhowells-fs/keys-next v7.3 next-20261027]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Jarkko-Sakkinen/KEYS-Expand-key-datalen-quotalen-to-unsigned-int/20261025-031009
base: linus/master
patch link: https://lore.kernel.org/r/20261025001105.1824178-6-jarkko%40kernel.org
patch subject: [PATCH v3 5/6] KEYS: Replace assoc_array with rhashtable
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20261028/202610281546.OMDCubFW-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 186e70f4e6a1521991d2340d3d49b23b1beff11f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261028/202610281546.OMDCubFW-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/202610281546.OMDCubFW-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
>> kernel/bpf/keys.c:32:30: error: no member named 'keys' in 'struct key'
32 | if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
| ~~~~~~~~~~~ ^
7 errors generated.
vim +32 kernel/bpf/keys.c
abaa0835b4f3810 Daniel Borkmann 2026-08-28 25
264d8fd2794fabe Daniel Borkmann 2026-08-28 26 struct bpf_key *bpf_lookup_keyring(void)
264d8fd2794fabe Daniel Borkmann 2026-08-28 27 {
264d8fd2794fabe Daniel Borkmann 2026-08-28 28 struct bpf_key *bkey;
264d8fd2794fabe Daniel Borkmann 2026-08-28 29
264d8fd2794fabe Daniel Borkmann 2026-08-28 30 if (!bpf_keyring)
264d8fd2794fabe Daniel Borkmann 2026-08-28 31 return NULL;
264d8fd2794fabe Daniel Borkmann 2026-08-28 @32 if (!READ_ONCE(bpf_keyring->keys.nr_leaves_on_tree) ||
264d8fd2794fabe Daniel Borkmann 2026-08-28 33 !READ_ONCE(bpf_keyring->restrict_link))
264d8fd2794fabe Daniel Borkmann 2026-08-28 34 return NULL;
264d8fd2794fabe Daniel Borkmann 2026-08-28 35
264d8fd2794fabe Daniel Borkmann 2026-08-28 36 bkey = kmalloc_obj(*bkey);
264d8fd2794fabe Daniel Borkmann 2026-08-28 37 if (!bkey)
264d8fd2794fabe Daniel Borkmann 2026-08-28 38 return NULL;
264d8fd2794fabe Daniel Borkmann 2026-08-28 39
264d8fd2794fabe Daniel Borkmann 2026-08-28 40 bkey->key = bpf_keyring;
264d8fd2794fabe Daniel Borkmann 2026-08-28 41 bkey->has_ref = false;
264d8fd2794fabe Daniel Borkmann 2026-08-28 42 return bkey;
264d8fd2794fabe Daniel Borkmann 2026-08-28 43 }
264d8fd2794fabe Daniel Borkmann 2026-08-28 44
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-28 7:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 0:10 [PATCH v3 0/6] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 1/6] KEYS: Expand key->{datalen,quotalen} to unsigned int Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 2/6] KEYS: Reject descriptions larger than KEY_MAX_DESC_SIZE Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 3/6] KEYS: Verify the key identity in __key_unlink_begin Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 4/6] KEYS: Introduce keyring_is_empty() Jarkko Sakkinen
2026-10-26 23:55 ` Eric Biggers
2026-10-27 0:01 ` Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 5/6] KEYS: Replace assoc_array with rhashtable Jarkko Sakkinen
2026-10-25 1:05 ` sashiko-bot
2026-10-25 3:35 ` Jarkko Sakkinen
2026-10-25 16:08 ` Jarkko Sakkinen
2026-10-27 1:29 ` Eric Biggers
2026-10-27 2:56 ` Jarkko Sakkinen
2026-10-27 3:00 ` Jarkko Sakkinen
2026-10-28 7:28 ` kernel test robot [this message]
2026-10-28 20:13 ` Jarkko Sakkinen
2026-10-25 0:10 ` [PATCH v3 6/6] lib: Remove assoc_array Jarkko Sakkinen
2026-10-26 23:57 ` Eric Biggers
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=202610281546.OMDCubFW-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=tgraf@suug.ch \
/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