From: Andy Lutomirski <luto@amacapital.net>
To: Borislav Petkov <bp@alien8.de>
Cc: Barret Rhoden <brho@google.com>,
austin@google.com,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Rik van Riel <riel@surriel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: AVX register corruption from signal delivery
Date: Tue, 26 Nov 2019 14:30:10 -0800 [thread overview]
Message-ID: <EFBC6B60-D0EC-4518-A38E-076D3933AA0E@amacapital.net> (raw)
In-Reply-To: <20191126221328.GH31379@zn.tnic>
> On Nov 26, 2019, at 2:14 PM, Borislav Petkov <bp@alien8.de> wrote:
>
> On Tue, Nov 26, 2019 at 04:23:40PM -0500, Barret Rhoden wrote:
>> Thanks; config attached. I've been able to recreate it in QEMU with at
>> least 2 cores.
>
> Yap, I can too, in my VM.
>
> Btw, would you guys like to submit that reproducer test program
>
> https://bugzilla.kernel.org/attachment.cgi?id=286073
>
> into the kernel selftests pile here:
>
> tools/testing/selftests/x86/
>
> ?
>
> It needs proper cleanup to fit kernel coding style but it could be a
> good start for collecting interesting FPU test cases.
If we do this, we should have selftests/x86/slow or otherwise have a fast vs slow mode. I really like that the entire suite takes under 2s.
next prev parent reply other threads:[~2019-11-26 22:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 19:49 AVX register corruption from signal delivery Barret Rhoden
2019-11-26 20:20 ` Sebastian Andrzej Siewior
2019-11-26 21:23 ` Barret Rhoden
2019-11-26 22:13 ` Borislav Petkov
2019-11-26 22:30 ` Andy Lutomirski [this message]
2019-11-26 23:00 ` Borislav Petkov
2019-11-27 12:42 ` [PATCH] x86/fpu: Don't cache access to fpu_fpregs_owner_ctx Sebastian Andrzej Siewior
2019-11-27 14:07 ` Borislav Petkov
2019-11-27 18:42 ` Barret Rhoden
2019-11-28 8:53 ` [PATCH v2] " Sebastian Andrzej Siewior
2019-11-28 9:22 ` [tip: x86/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2019-11-29 16:57 ` [PATCH v2] " David Laight
2019-11-29 17:08 ` 'Sebastian Andrzej Siewior'
2019-11-27 15:46 ` [PATCH] " Rik van Riel
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=EFBC6B60-D0EC-4518-A38E-076D3933AA0E@amacapital.net \
--to=luto@amacapital.net \
--cc=austin@google.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=brho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=riel@surriel.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;
as well as URLs for NNTP newsgroup(s).