[vbabka:objext_split 10/14] mm/kasan/../slab.h:702:47: error: no member named '_ctref' in 'struct slabobj_ext'

kernel test robot <[email protected]>
Newsgroups dev.linux.lists.llvm,dev.linux.lists.oe-kbuild-all
Message-ID <[email protected]>
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/[email protected]/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/[email protected]/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 <[email protected]>
| Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/

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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.