From: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
To: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
Cc: Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
Tom Yan <tom.ty89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Matt Fleming
<matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] x86/efi-bgrt: Switch pr_err() to pr_debug() for invalid BGRT
Date: Mon, 29 Jun 2015 07:00:22 -0700 [thread overview]
Message-ID: <20150629140022.GA22374@x> (raw)
In-Reply-To: <20150629131305.GB13113-fF5Pk5pvG8Y@public.gmane.org>
On Mon, Jun 29, 2015 at 03:13:05PM +0200, Borislav Petkov wrote:
> On Mon, Jun 29, 2015 at 01:06:42PM +0100, Matt Fleming wrote:
> > From: Matt Fleming <matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> >
> > It's totally legitimate, per the ACPI spec, for the firmware to set the
> > BGRT 'status' field to zero to indicate that the BGRT image isn't being
> > displayed, and we shouldn't be printing an error message in that case
> > because it's just noise for users. So swap pr_err() for pr_debug().
> >
> > However, Josh points that out it still makes sense to test the validity
> > of the upper 7 bits of the 'status' field, since they're marked as
> > "reserved" in the spec and must be zero. If firmware violates this it
> > really *is* an error.
>
> Sounds to me this should be
>
> pr_warn(FW_WARN "... );
>
> then, no?
>
> So that it hopefully gets caught at early testing when fw can still be
> fixed...?
>
> Better yet FW_BUG even...
Definitely not FW_BUG. The field is reserved *now*; it would be
legitimate for a new version of the BGRT spec to define one of those
bits for something else.
- Josh Triplett
next prev parent reply other threads:[~2015-06-29 14:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 12:06 [PATCH] x86/efi-bgrt: Switch pr_err() to pr_debug() for invalid BGRT Matt Fleming
[not found] ` <1435579602-6612-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-06-29 13:13 ` Borislav Petkov
[not found] ` <20150629131305.GB13113-fF5Pk5pvG8Y@public.gmane.org>
2015-06-29 14:00 ` Josh Triplett [this message]
2015-06-29 14:17 ` Borislav Petkov
[not found] ` <20150629141724.GG12383-fF5Pk5pvG8Y@public.gmane.org>
2015-06-29 14:45 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-06-29 14:49 ` Matt Fleming
[not found] ` <20150629144940.GF28334-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-06-29 14:53 ` josh-iaAMLnmF4UmaiuxdJuQwMA
2015-06-29 15:44 ` Borislav Petkov
2015-06-29 16:35 ` josh
2015-06-30 9:31 ` Matt Fleming
2015-06-29 14:02 ` Josh Triplett
2015-06-29 21:52 ` Tom Yan
2015-06-30 10:00 ` Matt Fleming
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=20150629140022.GA22374@x \
--to=josh-iaamlnmf4umaiuxdjuqwma@public.gmane.org \
--cc=bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=matt.fleming-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=tom.ty89-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.