From: Josef Bacik <jbacik@fb.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Andrey Borzenkov <arvidjaar@gmail.com>, mchang@suse.com
Subject: Re: [PATCH 1/3] efinet: handle get_status() properly
Date: Wed, 5 Aug 2015 16:50:06 -0400 [thread overview]
Message-ID: <55C276FE.2010605@fb.com> (raw)
In-Reply-To: <55C27474.9010504@fb.com>
On 08/05/2015 04:39 PM, Josef Bacik wrote:
> On 08/05/2015 04:32 PM, Vladimir 'phcoder' Serbinenko wrote:
>> This patch improperly assumes that GRUB is the only thing in EFI that
>> transmits. Your patch surely fixed your machine but likely breaks some
>> other machines. Could you instead make an explicit check for (void *)1
>> and add a comment on which machine it's necessary?
>>
>
> Yeah this is kind of a crap trade-off I know. The problem is this is
> just on one box I'm testing with, we've got _a metric shit ton_ of
> boxes, if one of them returns 0x2 suddenly it can't be provisioned. I
> realize this is racey with other things on UEFI doing stuff, but I don't
> have a better answer. Maybe a range check for obviously bogus
> addresses? Or maybe once we get a non-NULL from GetStatus() we call it
> again until we get a NULL from GetStatus()? Thanks,
>
Could also just add a variable along the lines of
"net_known_shitty_efi_firmware" and only do this if that variable is
set, that way it's the users choice to work around this or not. Thanks,
Josef
next prev parent reply other threads:[~2015-08-05 20:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 18:36 [PATCH 1/3] efinet: handle get_status() properly Josef Bacik
2015-08-05 18:36 ` [PATCH 2/3] net: add local route when creating link local ipv6 interface Josef Bacik
2015-08-07 8:38 ` Andrei Borzenkov
2015-08-05 18:36 ` [PATCH 3/3] net: fix ipv6 routing Josef Bacik
2015-08-09 14:58 ` Andrei Borzenkov
2015-08-10 14:00 ` Josef Bacik
2015-08-10 14:07 ` Andrei Borzenkov
2015-08-05 20:04 ` [PATCH 1/3] efinet: handle get_status() properly Andrei Borzenkov
2015-08-05 20:26 ` Josef Bacik
2015-08-05 20:32 ` Vladimir 'phcoder' Serbinenko
2015-08-05 20:39 ` Josef Bacik
2015-08-05 20:50 ` Josef Bacik [this message]
2015-08-05 20:52 ` Vladimir 'phcoder' Serbinenko
2015-08-06 3:42 ` Andrei Borzenkov
2015-08-06 14:26 ` Josef Bacik
2015-08-05 20:57 ` Seth Goldberg
2015-08-06 17:49 ` [PATCH V2] efinet: handle get_status() on buggy firmware properly Josef Bacik
2015-08-09 13:48 ` Andrei Borzenkov
-- strict thread matches above, loose matches on Subject: below --
2015-08-05 17:50 [PATCH 0/3] fix ipv6 support Josef Bacik
2015-08-05 17:50 ` [PATCH 1/3] efinet: handle get_status() properly Josef Bacik
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=55C276FE.2010605@fb.com \
--to=jbacik@fb.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=mchang@suse.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;
as well as URLs for NNTP newsgroup(s).