From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"hpa@zytor.com" <hpa@zytor.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Matt Fleming <matt@codeblueprint.co.uk>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 5/5] efi/runtime-wrappers: detect FW irq flag corruption
Date: Thu, 21 Apr 2016 18:18:14 +0100 [thread overview]
Message-ID: <20160421171814.GB3078@leverpostej> (raw)
In-Reply-To: <CAKv+Gu-Sou_-UgBwrj939JQr8M5=ScZZ4M9Y-hRUa8WrkwBK7Q@mail.gmail.com>
On Thu, Apr 21, 2016 at 07:05:32PM +0200, Ard Biesheuvel wrote:
> On 21 April 2016 at 13:35, Mark Rutland <mark.rutland@arm.com> wrote:
> > @@ -25,8 +27,11 @@
> > #define efi_call_virt(f, args...) \
> > ({ \
> > efi_status_t __s; \
> > + unsigned long flags; \
> > arch_efi_call_virt_setup(); \
> > + local_save_flags(flags); \
> > __s = arch_efi_call_virt(f, args); \
> > + efi_call_virt_check_flags(flags, __stringify(f)); \
> > arch_efi_call_virt_teardown(); \
> > __s; \
> > })
> > @@ -35,12 +40,29 @@
> > #ifndef __efi_call_virt
> > #define __efi_call_virt(f, args...) \
> > ({ \
> > + unsigned long flags; \
> > arch_efi_call_virt_setup(); \
> > + local_irq_save(flags); \
>
> We shouldn't disable interrupts here. I assume this is a typo, and you
> intended to use local_save_flags() as above?
Oh, yes. That's an impressive mistake on my behalf; thanks for spotting
that!
I've been seeing issues with GetVariable and GetNextVariable, which
happen to only exercise the correct macro above.
> Other than that, this series looks fine to me.
>
> With the above fixed:
>
> For the series (except the x86 patch)
>
> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cheers!
Mark.
prev parent reply other threads:[~2016-04-21 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461238529-12810-1-git-send-email-mark.rutland@arm.com>
2016-04-21 11:35 ` [PATCHv2 1/5] efi/runtime-wrappers: add {__,}efi_call_virt templates Mark Rutland
2016-04-21 11:42 ` Leif Lindholm
2016-04-21 12:55 ` Mark Rutland
2016-04-21 14:19 ` Mark Rutland
2016-04-21 11:35 ` [PATCHv2 2/5] arm64/efi: move to generic {__,}efi_call_virt Mark Rutland
2016-04-21 16:48 ` Will Deacon
2016-04-21 16:58 ` Mark Rutland
2016-04-21 11:35 ` [PATCHv2 3/5] arm/efi: " Mark Rutland
2016-04-21 11:35 ` [PATCHv2 4/5] x86/efi: " Mark Rutland
2016-04-21 11:35 ` [PATCHv2 5/5] efi/runtime-wrappers: detect FW irq flag corruption Mark Rutland
2016-04-21 17:05 ` Ard Biesheuvel
2016-04-21 17:18 ` Mark Rutland [this message]
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=20160421171814.GB3078@leverpostej \
--to=mark.rutland@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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