From: kernel test robot <lkp@intel.com>
To: Sasha Levin <sashal@kernel.org>,
pasha.tatashin@soleen.com, rppt@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
pratyush@kernel.org, linux-kernel@vger.kernel.org,
surenb@google.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] kexec: allow KEXEC_HANDOVER to build with COMPILE_TEST
Date: Thu, 5 Feb 2026 10:05:59 +0800 [thread overview]
Message-ID: <202602051021.dhUjHKwO-lkp@intel.com> (raw)
In-Reply-To: <20260204182816.2463931-1-sashal@kernel.org>
Hi Sasha,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.19-rc8 next-20260204]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Sasha-Levin/kexec-allow-KEXEC_HANDOVER-to-build-with-COMPILE_TEST/20260205-023202
base: linus/master
patch link: https://lore.kernel.org/r/20260204182816.2463931-1-sashal%40kernel.org
patch subject: [PATCH] kexec: allow KEXEC_HANDOVER to build with COMPILE_TEST
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260205/202602051021.dhUjHKwO-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/20260205/202602051021.dhUjHKwO-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/202602051021.dhUjHKwO-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> mm/memfd_luo.c:316:10: warning: format specifies type 'unsigned long long' but the argument has type 'phys_addr_t' (aka 'unsigned int') [-Wformat]
315 | pr_warn_ratelimited("Unable to restore folio at physical address: %llx\n",
| ~~~~
| %x
316 | phys);
| ^~~~
include/linux/printk.h:722:49: note: expanded from macro 'pr_warn_ratelimited'
722 | printk_ratelimited(KERN_WARNING pr_fmt(fmt), ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:706:17: note: expanded from macro 'printk_ratelimited'
706 | printk(fmt, ##__VA_ARGS__); \
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:512:60: note: expanded from macro 'printk'
512 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:484:19: note: expanded from macro 'printk_index_wrap'
484 | _p_func(_fmt, ##__VA_ARGS__); \
| ~~~~ ^~~~~~~~~~~
mm/memfd_luo.c:372:11: warning: format specifies type 'unsigned long long' but the argument has type 'phys_addr_t' (aka 'unsigned int') [-Wformat]
371 | pr_err("Unable to restore folio at physical address: %llx\n",
| ~~~~
| %x
372 | phys);
| ^~~~
include/linux/printk.h:555:33: note: expanded from macro 'pr_err'
555 | printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:512:60: note: expanded from macro 'printk'
512 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
| ~~~ ^~~~~~~~~~~
include/linux/printk.h:484:19: note: expanded from macro 'printk_index_wrap'
484 | _p_func(_fmt, ##__VA_ARGS__); \
| ~~~~ ^~~~~~~~~~~
2 warnings generated.
--
>> kernel/liveupdate/kexec_handover.c:25:10: fatal error: 'asm/early_ioremap.h' file not found
25 | #include <asm/early_ioremap.h>
| ^~~~~~~~~~~~~~~~~~~~~
1 error generated.
--
>> kernel/liveupdate/kexec_handover_debugfs.c:99:29: warning: format specifies type 'unsigned long long' but the argument has type 'phys_addr_t' (aka 'unsigned int') [-Wformat]
99 | seq_printf(m, "0x%llx\n", kho_scratch[i].addr);
| ~~~~ ^~~~~~~~~~~~~~~~~~~
| %x
kernel/liveupdate/kexec_handover_debugfs.c:108:29: warning: format specifies type 'unsigned long long' but the argument has type 'phys_addr_t' (aka 'unsigned int') [-Wformat]
108 | seq_printf(m, "0x%llx\n", kho_scratch[i].size);
| ~~~~ ^~~~~~~~~~~~~~~~~~~
| %x
2 warnings generated.
vim +25 kernel/liveupdate/kexec_handover.c
c609c144b0e8db kernel/kexec_handover.c Alexander Graf 2025-05-09 24
c609c144b0e8db kernel/kexec_handover.c Alexander Graf 2025-05-09 @25 #include <asm/early_ioremap.h>
c609c144b0e8db kernel/kexec_handover.c Alexander Graf 2025-05-09 26
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-05 2:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 18:28 [PATCH] kexec: allow KEXEC_HANDOVER to build with COMPILE_TEST Sasha Levin
2026-02-04 22:32 ` Suren Baghdasaryan
2026-02-05 0:22 ` kernel test robot
2026-02-05 2:05 ` kernel test robot
2026-02-05 2:05 ` kernel test robot [this message]
2026-02-05 12:00 ` Mike Rapoport
2026-02-05 12:07 ` Pratyush Yadav
2026-02-05 12:05 ` kernel test robot
2026-02-06 21:52 ` [PATCH v2] " Sasha Levin
2026-02-07 7:40 ` Mike Rapoport
2026-02-07 16:06 ` Pasha Tatashin
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=202602051021.dhUjHKwO-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=surenb@google.com \
/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