From: Xin Li <xin@zytor.com>
To: kernel test robot <lkp@intel.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, peterz@infradead.org,
andrew.cooper3@citrix.com, stable@vger.kernel.org
Subject: Re: [PATCH v1 1/1] x86/fred/signal: Prevent single-step upon ERETU completion
Date: Thu, 22 May 2025 10:33:36 -0700 [thread overview]
Message-ID: <83b013fb-2057-4097-ac8c-b5c38d019a0f@zytor.com> (raw)
In-Reply-To: <202505230141.4YBHhrPI-lkp@intel.com>
On 5/22/2025 10:20 AM, kernel test robot wrote:
> Hi Xin,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on 6a7c3c2606105a41dde81002c0037420bc1ddf00]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Xin-Li-Intel/x86-fred-signal-Prevent-single-step-upon-ERETU-completion/20250522-140954
> base: 6a7c3c2606105a41dde81002c0037420bc1ddf00
> patch link: https://lore.kernel.org/r/20250522060549.2882444-1-xin%40zytor.com
> patch subject: [PATCH v1 1/1] x86/fred/signal: Prevent single-step upon ERETU completion
> config: i386-buildonly-randconfig-003-20250522 (https://download.01.org/0day-ci/archive/20250523/202505230141.4YBHhrPI-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250523/202505230141.4YBHhrPI-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/202505230141.4YBHhrPI-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> In file included from arch/x86/kernel/signal_32.c:32:
> arch/x86/include/asm/sighandling.h: In function 'prevent_single_step_upon_eretu':
>>> arch/x86/include/asm/sighandling.h:44:21: error: 'struct pt_regs' has no member named 'fred_ss'
> 44 | regs->fred_ss.swevent = 0;
> | ^~
>
Hmm, this statement is under IS_ENABLED(CONFIG_X86_FRED), which should
be a compile time FALSE with i386. Why it is still being compiled?
Thanks!
Xin
next prev parent reply other threads:[~2025-05-22 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 6:05 Xin Li (Intel)
2025-05-22 7:20 ` H. Peter Anvin
2025-05-22 17:10 ` Xin Li
2025-05-22 17:20 ` kernel test robot
2025-05-22 17:33 ` Xin Li [this message]
2025-05-22 17:51 ` Andrew Cooper
2025-05-23 6:23 ` Xin Li
2025-05-22 17:54 ` Dave Hansen
2025-05-23 6:24 ` Xin Li
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=83b013fb-2057-4097-ac8c-b5c38d019a0f@zytor.com \
--to=xin@zytor.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®