From: kernel test robot <lkp@intel.com>
To: Hou Wenlong <houwenlong.hwl@antgroup.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Hou Wenlong <houwenlong.hwl@antgroup.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <kees@kernel.org>, Josh Poimboeuf <jpoimboe@kernel.org>,
FUJITA Tomonori <fujita.tomonori@gmail.com>,
Sohil Mehta <sohil.mehta@intel.com>,
"Xin Li (Intel)" <xin@zytor.com>,
Mostafa Saleh <smostafa@google.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH] x86_64/bug: Handle __WARN_printf() trap in early_fixup_exception()
Date: Sat, 10 Jan 2026 03:45:30 +0100 [thread overview]
Message-ID: <202601100329.ndS6mKRm-lkp@intel.com> (raw)
In-Reply-To: <97dd5c5b5e92d48ffbc95fb1357dfbbbf0d12a1e.1767960698.git.houwenlong.hwl@antgroup.com>
Hi Hou,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.19-rc4 next-20260109]
[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/Hou-Wenlong/x86_64-bug-Handle-__WARN_printf-trap-in-early_fixup_exception/20260109-204012
base: linus/master
patch link: https://lore.kernel.org/r/97dd5c5b5e92d48ffbc95fb1357dfbbbf0d12a1e.1767960698.git.houwenlong.hwl%40antgroup.com
patch subject: [PATCH] x86_64/bug: Handle __WARN_printf() trap in early_fixup_exception()
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260110/202601100329.ndS6mKRm-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260110/202601100329.ndS6mKRm-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/202601100329.ndS6mKRm-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/mm/extable.c:414:7: error: call to undeclared function 'handle_bug'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
414 | if (handle_bug(regs))
| ^
1 error generated.
vim +/handle_bug +414 arch/x86/mm/extable.c
376
377 /* Restricted version used during very early boot */
378 void __init early_fixup_exception(struct pt_regs *regs, int trapnr)
379 {
380 /* Ignore early NMIs. */
381 if (trapnr == X86_TRAP_NMI)
382 return;
383
384 if (early_recursion_flag > 2)
385 goto halt_loop;
386
387 /*
388 * Old CPUs leave the high bits of CS on the stack
389 * undefined. I'm not sure which CPUs do this, but at least
390 * the 486 DX works this way.
391 * Xen pv domains are not using the default __KERNEL_CS.
392 */
393 if (!xen_pv_domain() && regs->cs != __KERNEL_CS)
394 goto fail;
395
396 /*
397 * The full exception fixup machinery is available as soon as
398 * the early IDT is loaded. This means that it is the
399 * responsibility of extable users to either function correctly
400 * when handlers are invoked early or to simply avoid causing
401 * exceptions before they're ready to handle them.
402 *
403 * This is better than filtering which handlers can be used,
404 * because refusing to call a handler here is guaranteed to
405 * result in a hard-to-debug panic.
406 *
407 * Keep in mind that not all vectors actually get here. Early
408 * page faults, for example, are special.
409 */
410 if (fixup_exception(regs, trapnr, regs->orig_ax, 0))
411 return;
412
413 if (trapnr == X86_TRAP_UD) {
> 414 if (handle_bug(regs))
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-10 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 12:21 Hou Wenlong
2026-01-10 2:45 ` kernel test robot [this message]
2026-01-10 3:47 ` [PATCH v2] x86/bug: " Hou Wenlong
2026-01-12 7:44 ` Peter Zijlstra
2026-01-12 8:38 ` Hou Wenlong
2026-01-19 6:48 ` Hou Wenlong
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=202601100329.ndS6mKRm-lkp@intel.com \
--to=lkp@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=fujita.tomonori@gmail.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=smostafa@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.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
all inboxes | Powered by JetHome®