From: Dave Hansen <dave.hansen@intel.com>
To: Alexandre Chartre <alexandre.chartre@oracle.com>,
x86@kernel.org, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, daniel.sneddon@linux.intel.com,
pawan.kumar.gupta@linux.intel.com, tglx@linutronix.de,
konrad.wilk@oracle.com, peterz@infradead.org,
gregkh@linuxfoundation.org, seanjc@google.com,
andrew.cooper3@citrix.com, dave.hansen@linux.intel.com,
nik.borisov@suse.com, kpsingh@kernel.org, longman@redhat.com,
bp@alien8.de, pbonzini@redhat.com
Subject: Re: [PATCH] x86/bhi: BHI mitigation can trigger warning in #DB handler
Date: Thu, 23 May 2024 07:28:44 -0700 [thread overview]
Message-ID: <a04d82be-a0d6-4e53-b47c-dba8402199e7@intel.com> (raw)
In-Reply-To: <20240523123322.3326690-1-alexandre.chartre@oracle.com>
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?
next prev parent reply other threads:[~2024-05-23 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 12:33 [PATCH] x86/bhi: BHI mitigation can trigger warning in #DB handler Alexandre Chartre
2024-05-23 12:36 ` Greg KH
2024-05-23 12:42 ` Andrew Cooper
2024-05-23 12:59 ` Alexandre Chartre
2024-05-23 14:59 ` Andrew Cooper
2024-05-23 14:28 ` Dave Hansen [this message]
2024-05-23 14:52 ` Alexandre Chartre
2024-05-23 15:34 ` Andrew Cooper
2024-05-23 15:36 ` Dave Hansen
2024-05-23 17:03 ` Alexandre Chartre
2024-05-23 17:53 ` Andrew Cooper
2024-05-23 18:27 ` Alexandre Chartre
2024-05-23 18:30 ` Alexandre Chartre
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=a04d82be-a0d6-4e53-b47c-dba8402199e7@intel.com \
--to=dave.hansen@intel.com \
--cc=alexandre.chartre@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.wilk@oracle.com \
--cc=kpsingh@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--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