From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [axboe-block:io_uring-handle 5/5] ld.lld: error: undefined symbol: get_path_from_fd
Date: Wed, 30 Apr 2025 10:19:43 +0800 [thread overview]
Message-ID: <202504301022.hc3VqjwL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git io_uring-handle
head: 545e6e52fadd5e04524e00f23b59635496318716
commit: 0519531750fa77b52759fc3c717486f69e4d69bc [5/5] io_uring: add support for IORING_OP_OPEN_BY_HANDLE
config: x86_64-buildonly-randconfig-001-20250430 (https://download.01.org/0day-ci/archive/20250430/202504301022.hc3VqjwL-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504301022.hc3VqjwL-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/202504301022.hc3VqjwL-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: get_path_from_fd
>>> referenced by openclose.c:546 (io_uring/openclose.c:546)
>>> vmlinux.o:(io_open_by_handle)
--
>> ld.lld: error: undefined symbol: may_decode_fh
>>> referenced by openclose.c:554 (io_uring/openclose.c:554)
>>> vmlinux.o:(io_open_by_handle)
--
>> ld.lld: error: undefined symbol: do_handle_to_path
>>> referenced by openclose.c:510 (io_uring/openclose.c:510)
>>> vmlinux.o:(io_open_by_handle)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-30 2:20 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=202504301022.hc3VqjwL-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).