[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a04d82be-a0d6-4e53-b47c-dba8402199e7@intel.com>
Date: Thu, 23 May 2024 07:28:44 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Alexandre Chartre <alexandre.chartre@...cle.com>, x86@...nel.org,
kvm@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, daniel.sneddon@...ux.intel.com,
pawan.kumar.gupta@...ux.intel.com, tglx@...utronix.de,
konrad.wilk@...cle.com, peterz@...radead.org, gregkh@...uxfoundation.org,
seanjc@...gle.com, andrew.cooper3@...rix.com, dave.hansen@...ux.intel.com,
nik.borisov@...e.com, kpsingh@...nel.org, longman@...hat.com, bp@...en8.de,
pbonzini@...hat.com
Subject: Re: [PATCH] x86/bhi: BHI mitigation can trigger warning in #DB
handler
On 5/23/24 05:33, Alexandre Chartre wrote:
> The problem can be reproduced with the following sequence:
>
> $ cat sysenter_step.c
> int main()
> { asm("pushf; pop %ax; bts $8,%ax; push %ax; popf; sysenter"); }
>
> $ gcc -o sysenter_step sysenter_step.c
>
> $ ./sysenter_step
> Segmentation fault (core dumped)
>
> The program is expected to crash, and the #DB handler will issue a warning.
Should we wrap up this gem and put it with the other entry selftests?
Powered by blists - more mailing lists