From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: [bigeasy-staging:futex_local_v10 16/21] fork.c:undefined reference to `futex_hash_free'
Date: Wed, 12 Mar 2025 10:22:27 +0800 [thread overview]
Message-ID: <202503121056.u2KwsVBf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/bigeasy/staging.git futex_local_v10
head: 1a9133756e6eeef39468a2076cf712331180694b
commit: ccbfa01ed2ba7957ac35cd762f8a26dbf3e1db97 [16/21] futex: Remove superfluous state
config: sh-randconfig-001-20250312 (https://download.01.org/0day-ci/archive/20250312/202503121056.u2KwsVBf-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250312/202503121056.u2KwsVBf-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/202503121056.u2KwsVBf-lkp@intel.com/
All errors (new ones prefixed by >>):
sh4-linux-ld: kernel/fork.o: in function `mmput':
>> fork.c:(.text+0xe78): undefined reference to `futex_hash_free'
sh4-linux-ld: kernel/fork.o: in function `copy_process':
>> fork.c:(.text+0x2090): undefined reference to `futex_hash_allocate_default'
sh4-linux-ld: kernel/futex/core.o: in function `exit_pi_state_list':
core.c:(.text+0x3d0): undefined reference to `futex_get_private_hash'
>> sh4-linux-ld: core.c:(.text+0x3f8): undefined reference to `futex_hash_put'
sh4-linux-ld: core.c:(.text+0x4cc): undefined reference to `futex_hash_put'
sh4-linux-ld: core.c:(.text+0x4d8): undefined reference to `futex_put_private_hash'
sh4-linux-ld: kernel/futex/pi.o: in function `class_hb_destructor.isra.0':
>> pi.c:(.text+0x24c): undefined reference to `futex_hash_put'
sh4-linux-ld: kernel/futex/pi.o: in function `futex_lock_pi':
pi.c:(.text+0xd08): undefined reference to `futex_hash_put'
sh4-linux-ld: kernel/futex/pi.o: in function `futex_unlock_pi':
>> pi.c:(.text+0xf80): undefined reference to `futex_hash_get'
sh4-linux-ld: kernel/futex/requeue.o: in function `requeue_pi_wake_futex':
>> requeue.c:(.text+0x1cc): undefined reference to `futex_hash_get'
sh4-linux-ld: kernel/futex/requeue.o: in function `class_hb_destructor.isra.0':
>> requeue.c:(.text+0x21c): undefined reference to `futex_hash_put'
sh4-linux-ld: kernel/futex/requeue.o: in function `futex_wait_requeue_pi':
requeue.c:(.text+0x98c): undefined reference to `futex_hash_put'
sh4-linux-ld: kernel/futex/waitwake.o: in function `class_hb_destructor.isra.0':
>> waitwake.c:(.text+0x10c): undefined reference to `futex_hash_put'
sh4-linux-ld: kernel/futex/waitwake.o: in function `futex_wait_multiple_setup':
waitwake.c:(.text+0x8b4): undefined reference to `futex_get_private_hash'
sh4-linux-ld: waitwake.c:(.text+0x8bc): undefined reference to `futex_put_private_hash'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-03-12 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 2:22 kernel test robot [this message]
2025-03-12 14:35 ` [bigeasy-staging:futex_local_v10 16/21] fork.c:undefined reference to `futex_hash_free' Sebastian Andrzej Siewior
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=202503121056.u2KwsVBf-lkp@intel.com \
--to=lkp@intel.com \
--cc=bigeasy@linutronix.de \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox