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 13/19] mm/slub.c:2098:1: error: expected identifier or '('
Date: Fri, 10 Jul 2026 17:57:45 +0800 [thread overview]
Message-ID: <202607101753.3XTkPSvA-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: c4923e2e532497a14255f7a0ff21e2a0c2b79445
commit: 9028e3e3942a1f9fcdfe06b498814fae5e3171b0 [13/19] mm/slab: abstract slabobj_ext.ref access
config: i386-randconfig-015-20260710 (https://download.01.org/0day-ci/archive/20260710/202607101753.3XTkPSvA-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/20260710/202607101753.3XTkPSvA-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/202607101753.3XTkPSvA-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/slub.c:2098:1: error: expected identifier or '('
2098 | {
| ^
1 error generated.
vim +2098 mm/slub.c
0bedcc66d2a43a Vlastimil Babka 2023-10-03 2095
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2096) static inline void handle_failed_objexts_alloc(struct slab *slab,
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2097) unsigned long obj_exts, struct slabobj_ext *vec);
0bedcc66d2a43a Vlastimil Babka 2023-10-03 @2098 {
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2099) vec = slab_obj_ext_shift_codetag_ref(slab, vec);
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2100)
0bedcc66d2a43a Vlastimil Babka 2023-10-03 2101 /*
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2102 * If vector previously failed to allocate then we have live
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2103 * objects with no tag reference. Mark all references in this
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2104 * vector as empty to avoid warnings later on.
0bedcc66d2a43a Vlastimil Babka 2023-10-03 2105 */
7612833192d56a Alexei Starovoitov 2025-09-08 2106 if (obj_exts == OBJEXTS_ALLOC_FAIL) {
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2107 unsigned int i;
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2108
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2109) for (i = 0; i < slab->objects; i++)
9028e3e3942a1f Vlastimil Babka (SUSE 2026-07-08 2110) set_codetag_empty(&vec[i]._ctref);
0bedcc66d2a43a Vlastimil Babka 2023-10-03 2111 }
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2112 }
09c46563ff6d5f Suren Baghdasaryan 2024-03-21 2113
:::::: The code at line 2098 was first introduced by commit
:::::: 0bedcc66d2a43a50ab660273842f4737a293dd8a mm/slab: move memcg related functions from slab.h to slub.c
:::::: TO: Vlastimil Babka <vbabka@suse.cz>
:::::: CC: Vlastimil Babka <vbabka@suse.cz>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-10 9:58 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=202607101753.3XTkPSvA-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.