From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] EFI changes for v3.16
Date: Mon, 19 May 2014 11:51:29 +0100 [thread overview]
Message-ID: <20140519105129.GF4798@console-pimps.org> (raw)
In-Reply-To: <20140503130447.GW26088@console-pimps.org>
On Sat, 03 May, at 02:04:47PM, Matt Fleming wrote:
> Folks, please queue the following change for v3.16 from Borislav that
> uses the more strict kernel_fpu_{begin,end}() instead of the __*
> verisons that won't catch buggy use in interrupt context.
>
> The following changes since commit e33655a386ed3b26ad36fb97a47ebb1c2ca1e928:
>
> efivars: Add compatibility code for compat tasks (2014-04-17 13:53:53 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-next
>
> for you to fetch changes up to baa916f39b50ad91661534652110df40396acda0:
>
> x86/efi: Check for unsafe dealing with FPU state in irq ctxt (2014-05-03 06:39:25 +0100)
>
> ----------------------------------------------------------------
> * Use the more strict FPU handling functions before invoking EFI
> services to catch misuse in irq context - Borislav Petkov
Ping?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-05-19 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 13:04 [GIT PULL] EFI changes for v3.16 Matt Fleming
2014-05-19 10:51 ` Matt Fleming [this message]
2014-05-19 22:47 ` H. Peter Anvin
2014-05-19 23:10 ` Borislav Petkov
2014-05-20 0:17 ` H. Peter Anvin
2014-05-20 11:00 ` Borislav Petkov
2014-05-20 20:27 ` Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2014-04-19 10:06 Matt Fleming
2014-04-19 22:42 ` H. Peter Anvin
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=20140519105129.GF4798@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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