From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Môshe van der Sterre" <me-A/3C56C7qwM@public.gmane.org>,
"Josh Triplett" <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>,
"Andy Lutomirski" <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: BGRT warns again on my system
Date: Thu, 23 Jun 2016 13:01:47 +0100 [thread overview]
Message-ID: <20160623120147.GC8415@codeblueprint.co.uk> (raw)
In-Reply-To: <20160620053819.GB13633-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
On Mon, 20 Jun, at 01:38:19PM, Dave Young wrote:
>
> I may missed the background but I worry about who knows if it is meant
> to be used for BGRT image. Some vendors could respect the BGRT valid
> bit and just leave the address as a random address. And the random
> address could be a valid physical address though. It is possible to
> leak memory infomation.
>
> Could we reconsider about below commit? It may be a Windows 10 bug?
Valid concerns, but we can only go on anecdotal evidence from the
behaviour of the machines we see.
Even if it is a bug in Windows, if the firmware developers are writing
code that expects the bug, and users see pretty BIOS screens with
Windows but not in Linux, we usually try to be bug-compatible.
All of that is a long way of saying: It doesn't matter if it's a bug
or not, we should provide the same behaviour.
prev parent reply other threads:[~2016-06-23 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 20:46 BGRT warns again on my system Andy Lutomirski
[not found] ` <CALCETrUJ2QoUSYY82Q1BN3niasiunktnrmdE9Lmi2PZnCJRdag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-28 22:25 ` Josh Triplett
2016-05-29 4:09 ` Môshe van der Sterre
[not found] ` <574A6B5D.60200-A/3C56C7qwM@public.gmane.org>
2016-06-02 9:24 ` Matt Fleming
[not found] ` <20160602092438.GD2658-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-19 13:14 ` Môshe van der Sterre
[not found] ` <57669AC0.7010905-A/3C56C7qwM@public.gmane.org>
2016-06-19 14:38 ` Josh Triplett
2016-06-19 14:57 ` Môshe van der Sterre
2016-06-20 5:38 ` Dave Young
[not found] ` <20160620053819.GB13633-0VdLhd/A9Pl+NNSt+8eSiB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org>
2016-06-20 15:50 ` Josh Triplett
2016-06-23 12:01 ` Matt Fleming [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=20160623120147.GC8415@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=me-A/3C56C7qwM@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 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).