Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Liam R. Howlett (Oracle)" <liam@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [liam:maple_marks_v7.2_fixes 13/33] lib/maple_tree.c:744:29: error: conflicting types for 'mt_locked'
Date: Tue, 30 Jun 2026 10:28:15 +0800	[thread overview]
Message-ID: <202606301011.csHUFTZa-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/liam/linux.git maple_marks_v7.2_fixes
head:   1536d2bf9195cbde5a1dd7fa78fd6995a29b004f
commit: 6f34957a13773332ff09b7cd43aa9486f0adb285 [13/33] maple_tree: Fix dereference of rcu type
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20260630/202606301011.csHUFTZa-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260630/202606301011.csHUFTZa-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/202606301011.csHUFTZa-lkp@intel.com/

All errors (new ones prefixed by >>):

   lib/maple_tree.c:531:14: error: call to undeclared function 'mt_locked'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     531 |                                                        mt_locked(mas->tree)));
         |                                                        ^
>> lib/maple_tree.c:744:29: error: conflicting types for 'mt_locked'
     744 | static __always_inline bool mt_locked(const struct maple_tree *mt)
         |                             ^
   lib/maple_tree.c:531:14: note: previous implicit declaration is here
     531 |                                                        mt_locked(mas->tree)));
         |                                                        ^
   2 errors generated.


vim +/mt_locked +744 lib/maple_tree.c

19a462f06eb5a7 Liam R. Howlett 2023-07-14  743  
271f61a8b41dcd Liam R. Howlett 2023-11-01 @744  static __always_inline bool mt_locked(const struct maple_tree *mt)
54a611b605901c Liam R. Howlett 2022-09-06  745  {
54a611b605901c Liam R. Howlett 2022-09-06  746  	return mt_external_lock(mt) ? mt_lock_is_held(mt) :
54a611b605901c Liam R. Howlett 2022-09-06  747  		lockdep_is_held(&mt->ma_lock);
54a611b605901c Liam R. Howlett 2022-09-06  748  }
54a611b605901c Liam R. Howlett 2022-09-06  749  

:::::: The code at line 744 was first introduced by commit
:::::: 271f61a8b41dcd86e1ecc2e0455bcc071bc7dde4 maple_tree: clean up inlines for some functions

:::::: TO: Liam R. Howlett <Liam.Howlett@oracle.com>
:::::: CC: Andrew Morton <akpm@linux-foundation.org>

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

                 reply	other threads:[~2026-06-30  2:28 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=202606301011.csHUFTZa-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=liam@infradead.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