All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kees Cook <kees@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v4 3/4] init.h: Disable sanitizer coverage for __init and __head
Date: Fri, 25 Jul 2025 08:44:56 +0800	[thread overview]
Message-ID: <202507250816.PgMzyj4y-lkp@intel.com> (raw)
In-Reply-To: <20250724055029.3623499-3-kees@kernel.org>

Hi Kees,

kernel test robot noticed the following build errors:

[auto build test ERROR on next-20250723]
[also build test ERROR on v6.16-rc7]
[cannot apply to tip/x86/core arm64/for-next/core soc/for-next linus/master v6.16-rc7 v6.16-rc6 v6.16-rc5]
[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/Kees-Cook/arm64-Handle-KCOV-__init-vs-inline-mismatches/20250724-135311
base:   next-20250723
patch link:    https://lore.kernel.org/r/20250724055029.3623499-3-kees%40kernel.org
patch subject: [PATCH v4 3/4] init.h: Disable sanitizer coverage for __init and __head
config: arm64-randconfig-002-20250725 (https://download.01.org/0day-ci/archive/20250725/202507250816.PgMzyj4y-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250725/202507250816.PgMzyj4y-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/202507250816.PgMzyj4y-lkp@intel.com/

All errors (new ones prefixed by >>):

   aarch64-linux-ld: Unexpected GOT/PLT entries detected!
   aarch64-linux-ld: Unexpected run-time procedure linkages detected!
   aarch64-linux-ld: arch/arm/xen/enlighten.o: in function `xen_guest_init':
>> enlighten.c:(.init.text+0x364): undefined reference to `xen_efi_runtime_setup'

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

  reply	other threads:[~2025-07-25  0:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24  5:50 [PATCH v4 0/4] stackleak: Support Clang stack depth tracking Kees Cook
2025-07-24  5:50 ` Kees Cook
2025-07-24  5:50 ` [PATCH v4 1/4] arm64: Handle KCOV __init vs inline mismatches Kees Cook
2025-07-24  5:50   ` Kees Cook
2025-07-29  8:10   ` Will Deacon
2025-07-29  8:10     ` Will Deacon
2025-07-24  5:50 ` [PATCH v4 2/4] x86: " Kees Cook
2025-07-24  5:50   ` Kees Cook
2025-07-29  8:28   ` Mike Rapoport
2025-07-29  8:28     ` Mike Rapoport
2025-07-29  9:34   ` Arnd Bergmann
2025-07-29  9:34     ` Arnd Bergmann
2025-07-24  5:50 ` [PATCH v4 3/4] init.h: Disable sanitizer coverage for __init and __head Kees Cook
2025-07-24  5:50   ` Kees Cook
2025-07-25  0:44   ` kernel test robot [this message]
2025-07-24  5:50 ` [PATCH v4 4/4] kstack_erase: Support Clang stack depth tracking Kees Cook
2025-07-24  5:50   ` Kees Cook
2025-07-24 13:08   ` Nicolas Schier
2025-07-24 13:08     ` Nicolas Schier
2025-07-26  0:43 ` [PATCH v4 0/4] stackleak: " Nathan Chancellor
2025-07-26  0:43   ` Nathan Chancellor
2025-07-26  6:27   ` Kees Cook
2025-07-26  6:27     ` Kees Cook
2025-07-26 21:47   ` Kees Cook
2025-07-26 21:47     ` Kees Cook

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=202507250816.PgMzyj4y-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kees@kernel.org \
    --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 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.