From: kernel test robot <lkp@intel.com>
To: Harry Yoo <harry@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [harry:slab-allow-runtime-parameter-tuning-rfc-v1r1-wip 6/6] mm/slub.c:3173:44: error: no member named 'cache' in 'struct slab_sheaf'
Date: Wed, 13 May 2026 20:10:52 +0800 [thread overview]
Message-ID: <202605132022.8fbd7hvH-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/harry/linux.git slab-allow-runtime-parameter-tuning-rfc-v1r1-wip
head: 10c188407341817c6baf9dad9c788928f8387800
commit: 10c188407341817c6baf9dad9c788928f8387800 [6/6] mm/slab: allow changing sheaf_capacity at runtime
config: um-allnoconfig (https://download.01.org/0day-ci/archive/20260513/202605132022.8fbd7hvH-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260513/202605132022.8fbd7hvH-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/202605132022.8fbd7hvH-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/slub.c:3173:44: error: no member named 'cache' in 'struct slab_sheaf'
3173 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
>> mm/slub.c:3173:44: error: no member named 'cache' in 'struct slab_sheaf'
3173 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
>> mm/slub.c:3173:44: error: no member named 'cache' in 'struct slab_sheaf'
3173 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
mm/slub.c:3187:44: error: no member named 'cache' in 'struct slab_sheaf'
3187 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
mm/slub.c:3187:44: error: no member named 'cache' in 'struct slab_sheaf'
3187 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
mm/slub.c:3187:44: error: no member named 'cache' in 'struct slab_sheaf'
3187 | lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
| ~~~~~ ^
mm/slub.c:6042:8: error: use of undeclared label 'flush'
6042 | goto flush;
| ^
mm/slub.c:7962:39: error: use of undeclared identifier 'USHORT_MAX'
7962 | return max_t(unsigned int, capacity, USHORT_MAX);
| ^~~~~~~~~~
mm/slub.c:8641:26: error: no member named 'barn' in 'struct kmem_cache_node'
8641 | if (get_node(s, node)->barn)
| ~~~~~~~~~~~~~~~~~ ^
9 errors generated.
vim +3173 mm/slub.c
3162
3163 /*
3164 * The following two functions are used mainly in cases where we have to undo an
3165 * intended action due to a race or cpu migration. Thus they do not check the
3166 * empty or full sheaf limits for simplicity.
3167 */
3168
3169 static void barn_put_empty_sheaf(struct node_barn *barn, struct slab_sheaf *sheaf)
3170 {
3171 unsigned long flags;
3172
> 3173 lockdep_assert_held(this_cpu_ptr(&(sheaf->cache)->cpu_sheaves->lock));
3174
3175 spin_lock_irqsave(&barn->lock, flags);
3176
3177 list_add(&sheaf->barn_list, &barn->sheaves_empty);
3178 barn->nr_empty++;
3179
3180 spin_unlock_irqrestore(&barn->lock, flags);
3181 }
3182
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-13 12:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202605132022.8fbd7hvH-lkp@intel.com \
--to=lkp@intel.com \
--cc=harry@kernel.org \
--cc=llvm@lists.linux.dev \
--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