The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Rik van Riel <riel@surriel.com>, Thomas Gleixner <tglx@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com, Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>, Xin Li <xin@zytor.com>
Subject: Re: [PATCH] x86/entry: Read CR2 in asm entry stub to redcue NMI clobbering window
Date: Fri, 15 May 2026 02:09:03 +0800	[thread overview]
Message-ID: <202605150207.pvBEOHK3-lkp@intel.com> (raw)
In-Reply-To: <20260513121259.0aae7adc@fangorn>

Hi Rik,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/master]
[also build test ERROR on tip/x86/asm tip/x86/core linus/master v7.1-rc3 next-20260508]
[cannot apply to tip/auto-latest]
[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/Rik-van-Riel/x86-entry-Read-CR2-in-asm-entry-stub-to-redcue-NMI-clobbering-window/20260514-162554
base:   tip/master
patch link:    https://lore.kernel.org/r/20260513121259.0aae7adc%40fangorn
patch subject: [PATCH] x86/entry: Read CR2 in asm entry stub to redcue NMI clobbering window
config: i386-allnoconfig (https://download.01.org/0day-ci/archive/20260515/202605150207.pvBEOHK3-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/20260515/202605150207.pvBEOHK3-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/202605150207.pvBEOHK3-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/x86/include/asm/idtentry.h: Assembler messages:
>> arch/x86/include/asm/idtentry.h:627: Error: no such instruction: `idtentry_pf 14 asm_exc_page_fault exc_page_fault'


vim +627 arch/x86/include/asm/idtentry.h

   623	
   624	/* Raw exception entries which need extra work */
   625	DECLARE_IDTENTRY_RAW(X86_TRAP_UD,		exc_invalid_op);
   626	DECLARE_IDTENTRY_RAW(X86_TRAP_BP,		exc_int3);
 > 627	DECLARE_IDTENTRY_PF(X86_TRAP_PF,	exc_page_fault);
   628	

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

  parent reply	other threads:[~2026-05-14 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 16:12 [PATCH] x86/entry: Read CR2 in asm entry stub to redcue NMI clobbering window Rik van Riel
2026-05-13 16:31 ` Dave Hansen
2026-05-13 16:43   ` Rik van Riel
2026-05-13 17:12     ` Dave Hansen
2026-05-14 19:49       ` Andrew Cooper
2026-05-14 19:55         ` Dave Hansen
2026-05-14 18:09 ` kernel test robot [this message]
2026-05-14 22:54 ` 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=202605150207.pvBEOHK3-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=riel@surriel.com \
    --cc=tglx@kernel.org \
    --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