From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [ardb:x86-pie-v4-wip 20/21] arch/x86/boot/startup/relocate.c:19:26: sparse: sparse: invalid initializer
Date: Mon, 02 Feb 2026 04:08:54 +0800 [thread overview]
Message-ID: <202602020419.UqxaI892-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: arch/x86/boot/startup/relocate.c:19:26: sparse: sparse: invalid initializer"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Ard Biesheuvel <ardb@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git x86-pie-v4-wip
head: f706b38ea2701854b12c604e2b0eb94d229ea8f2
commit: fab6dd07b7371cff689427db19d85a874ed32a32 [20/21] x86/boot: Apply ELF PIE relocation fixups during startup
:::::: branch date: 8 hours ago
:::::: commit date: 8 hours ago
config: x86_64-randconfig-123-20260201 (https://download.01.org/0day-ci/archive/20260202/202602020419.UqxaI892-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260202/202602020419.UqxaI892-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/r/202602020419.UqxaI892-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/boot/startup/relocate.c:19:26: sparse: sparse: invalid initializer
>> arch/x86/boot/startup/relocate.c:19:59: sparse: sparse: need scalar for ++/--
arch/x86/boot/startup/relocate.c:24:26: sparse: sparse: invalid initializer
arch/x86/boot/startup/relocate.c:24:59: sparse: sparse: need scalar for ++/--
vim +19 arch/x86/boot/startup/relocate.c
fab6dd07b7371c Ard Biesheuvel 2026-01-31 11
fab6dd07b7371c Ard Biesheuvel 2026-01-31 12 void __init startup_relocate_kernel(void)
fab6dd07b7371c Ard Biesheuvel 2026-01-31 13 {
fab6dd07b7371c Ard Biesheuvel 2026-01-31 14 u64 *place;
fab6dd07b7371c Ard Biesheuvel 2026-01-31 15
fab6dd07b7371c Ard Biesheuvel 2026-01-31 16 if (!va_shift)
fab6dd07b7371c Ard Biesheuvel 2026-01-31 17 return;
fab6dd07b7371c Ard Biesheuvel 2026-01-31 18
fab6dd07b7371c Ard Biesheuvel 2026-01-31 @19 for (auto rela = rela_start; rela < rela_end; rela++) {
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-02-01 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 20:08 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-10 7:58 [ardb:x86-pie-v4-wip 20/21] arch/x86/boot/startup/relocate.c:19:26: sparse: sparse: invalid initializer kernel test robot
2026-04-30 16:35 kernel test robot
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=202602020419.UqxaI892-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 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.