From: kernel test robot <lkp@intel.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [vbabka:objext_split 10/14] mm/kasan/../slab.h:702:47: error: no member named '_ctref' in 'struct slabobj_ext'
Date: Thu, 09 Jul 2026 18:32:15 +0800 [thread overview]
Message-ID: <202607091829.wC2chgp4-lkp@intel.com> (raw)
Hi Vlastimil,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vbabka/linux.git objext_split
head: 8bd682e28958694beba958e2a3af94c6e1789819
commit: 510dc45196b1495bba6f15a6f3348ace5c983136 [10/14] mm/slab: abstract slabobj_ext.ref access
config: x86_64-buildonly-randconfig-006-20260709 (https://download.01.org/0day-ci/archive/20260709/202607091829.wC2chgp4-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607091829.wC2chgp4-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/202607091829.wC2chgp4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/kasan/generic.c:37:
>> mm/kasan/../slab.h:702:47: error: no member named '_ctref' in 'struct slabobj_ext'
702 | return &slab_obj_ext(slab, obj_exts, index)->_ctref;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
1 error generated.
vim +702 mm/kasan/../slab.h
694
695 static inline union codetag_ref *slab_obj_ext_codetag_ref(struct slab *slab,
696 unsigned long obj_exts, const void *obj)
697 {
698 unsigned int index;
699
700 index = obj_to_index(slab->slab_cache, slab, obj);
701
> 702 return &slab_obj_ext(slab, obj_exts, index)->_ctref;
703 }
704
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-09 10:33 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=202607091829.wC2chgp4-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.