From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org, mingo@kernel.org,
ricardo.neri-calderon@linux.intel.com, tglx@linutronix.de,
bp@suse.de, matt.fleming@intel.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/efi] x86/efi: Check for unsafe dealing with FPU state in irq ctxt
Date: Wed, 04 Jun 2014 15:17:30 -0700 [thread overview]
Message-ID: <538F9AFA.5050806@zytor.com> (raw)
In-Reply-To: <tip-baa916f39b50ad91661534652110df40396acda0@git.kernel.org>
On 06/04/2014 03:15 PM, tip-bot for Borislav Petkov wrote:
> Commit-ID: baa916f39b50ad91661534652110df40396acda0
> Gitweb: http://git.kernel.org/tip/baa916f39b50ad91661534652110df40396acda0
> Author: Borislav Petkov <bp@suse.de>
> AuthorDate: Fri, 25 Apr 2014 13:40:10 +0200
> Committer: Matt Fleming <matt.fleming@intel.com>
> CommitDate: Sat, 3 May 2014 06:39:25 +0100
>
> x86/efi: Check for unsafe dealing with FPU state in irq ctxt
>
> efi_call can happen in an irq context (pstore) and there we really need
> to make sure we're not scribbling over FPU state while we've interrupted
> a thread or kernel mode with a live FPU state. Therefore, use the
> kernel_fpu_begin/end() variants which do that check.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Cc: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
> Signed-off-by: Matt Fleming <matt.fleming@intel.com>
> ---
> arch/x86/include/asm/efi.h | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
I seem to have lost track of this... does this actually solve anything,
or does it just mean we'll explode hard?
-hpa
next parent reply other threads:[~2014-06-04 22:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-baa916f39b50ad91661534652110df40396acda0@git.kernel.org>
2014-06-04 22:17 ` H. Peter Anvin [this message]
2014-06-04 22:49 ` [tip:x86/efi] x86/efi: Check for unsafe dealing with FPU state in irq ctxt Borislav Petkov
2014-06-04 22:52 ` H. Peter Anvin
2014-06-05 0:19 ` Andy Lutomirski
2014-06-05 7:18 ` Borislav Petkov
2014-06-05 8:49 ` Matt Fleming
2014-06-05 9:02 ` Borislav Petkov
2014-06-05 15:44 ` Andy Lutomirski
2014-06-05 15:53 ` Borislav Petkov
2014-06-05 16:01 ` Andy Lutomirski
2014-06-05 16:08 ` Borislav Petkov
2014-06-05 16:14 ` Andy Lutomirski
2014-06-05 16:18 ` Borislav Petkov
2014-06-05 16:31 ` H. Peter Anvin
2014-06-05 16:35 ` Andy Lutomirski
2014-06-05 16:43 ` H. Peter Anvin
2014-06-05 16:37 ` Borislav Petkov
2014-06-05 16:43 ` H. Peter Anvin
2014-06-05 16:44 ` Borislav Petkov
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=538F9AFA.5050806@zytor.com \
--to=hpa@zytor.com \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.