All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [vbabka:objext_split 11/14] mm/slub.c:1201:13: error: implicit declaration of function 'obj_exts_in_object'; did you mean 'obj_exts_in_slab'?
Date: Thu, 09 Jul 2026 15:38:52 +0800	[thread overview]
Message-ID: <202607091514.vb217Kmc-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: 0923358e166406daf2533102ff371c4ba7f93bf3 [11/14] mm/slab: replace stride with obj_exts_in_object flag
config: xtensa-allnoconfig (https://download.01.org/0day-ci/archive/20260709/202607091514.vb217Kmc-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260709/202607091514.vb217Kmc-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/202607091514.vb217Kmc-lkp@intel.com/

All errors (new ones prefixed by >>):

   mm/slub.c: In function 'print_trailer':
>> mm/slub.c:1201:13: error: implicit declaration of function 'obj_exts_in_object'; did you mean 'obj_exts_in_slab'? [-Wimplicit-function-declaration]
    1201 |         if (obj_exts_in_object(slab))
         |             ^~~~~~~~~~~~~~~~~~
         |             obj_exts_in_slab


vim +1201 mm/slub.c

  1166	
  1167	static void print_trailer(struct kmem_cache *s, struct slab *slab, u8 *p)
  1168	{
  1169		unsigned int off;	/* Offset of last byte */
  1170		u8 *addr = slab_address(slab);
  1171	
  1172		print_tracking(s, p);
  1173	
  1174		print_slab_info(slab);
  1175	
  1176		pr_err("Object 0x%p @offset=%tu fp=0x%p\n\n",
  1177		       p, p - addr, get_freepointer(s, p));
  1178	
  1179		if (s->flags & SLAB_RED_ZONE)
  1180			print_section(KERN_ERR, "Redzone  ", p - s->red_left_pad,
  1181				      s->red_left_pad);
  1182		else if (p > addr + 16)
  1183			print_section(KERN_ERR, "Bytes b4 ", p - 16, 16);
  1184	
  1185		print_section(KERN_ERR,         "Object   ", p,
  1186			      min_t(unsigned int, s->object_size, PAGE_SIZE));
  1187		if (s->flags & SLAB_RED_ZONE)
  1188			print_section(KERN_ERR, "Redzone  ", p + s->object_size,
  1189				s->inuse - s->object_size);
  1190	
  1191		off = get_info_end(s);
  1192	
  1193		if (s->flags & SLAB_STORE_USER)
  1194			off += 2 * sizeof(struct track);
  1195	
  1196		if (slub_debug_orig_size(s))
  1197			off += sizeof(unsigned long);
  1198	
  1199		off += kasan_metadata_size(s, false);
  1200	
> 1201		if (obj_exts_in_object(slab))
  1202			off += sizeof(struct slabobj_ext);
  1203	
  1204		if (off != size_from_object(s))
  1205			/* Beginning of the filler is the free pointer */
  1206			print_section(KERN_ERR, "Padding  ", p + off,
  1207				      size_from_object(s) - off);
  1208	}
  1209	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-07-09  7:41 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=202607091514.vb217Kmc-lkp@intel.com \
    --to=lkp@intel.com \
    --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.