All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rojewski, Cezary" <cezary.rojewski@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi <linux-efi@vger.kernel.org>,
	"Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Subject: RE: [PATCH] efi/efivars: Set generic ops before loading SSDT
Date: Wed, 25 Nov 2020 10:18:09 +0000	[thread overview]
Message-ID: <e20e4ae680184d808a48312233415b0d@intel.com> (raw)
In-Reply-To: <CAMj1kXEY14MWoCnMHTzGpyC7V8=dF3fxT44tDqzRXZtXRRf87w@mail.gmail.com>

On 2020-11-23 11:53 PM, Ard Biesheuvel wrote:
> On Mon, 23 Nov 2020 at 16:11, Amadeusz Sławiński
> <amadeuszx.slawinski@linux.intel.com> wrote:
>>
>> Efivar allows for overriding of SSDT tables, however starting with
>> commit bf67fad19e493b ("efi: Use more granular check for availability for variable services")
>> this use case is broken. When loading SSDT generic ops should be set
>> first, however mentioned commit reversed order of operations. Fix this
>> by restoring original order of operations.
>>
>> Fixes: bf67fad19e493b ("efi: Use more granular check for availability for variable services")
>> Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
>> ---
>>   drivers/firmware/efi/efi.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
>> index 5e5480a0a32d..6c6eec044a97 100644
>> --- a/drivers/firmware/efi/efi.c
>> +++ b/drivers/firmware/efi/efi.c
>> @@ -390,10 +390,10 @@ static int __init efisubsys_init(void)
>>
>>          if (efi_rt_services_supported(EFI_RT_SUPPORTED_GET_VARIABLE |
>>                                        EFI_RT_SUPPORTED_GET_NEXT_VARIABLE_NAME)) {
>> -               efivar_ssdt_load();
>>                  error = generic_ops_register();
>>                  if (error)
>>                          goto err_put;
>> +               efivar_ssdt_load();
>>                  platform_device_register_simple("efivars", 0, NULL, 0);
>>          }
>>
> 
> Thanks. Queued as a fix.
> 

Sorry for the late reply. This is a good finding by Amadeo. If in any
case you need more credibility, feel free to apply my:

Tested-by: Cezary Rojewski <cezary.rojewski@intel.com>

Czarek


  reply	other threads:[~2020-11-25 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 17:28 [PATCH] efi/efivars: Set generic ops before loading SSDT Amadeusz Sławiński
2020-11-23 22:53 ` Ard Biesheuvel
2020-11-25 10:18   ` Rojewski, Cezary [this message]
2020-11-27 16:49 ` [tip: efi/urgent] " tip-bot2 for Amadeusz Sławiński

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=e20e4ae680184d808a48312233415b0d@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=ardb@kernel.org \
    --cc=linux-efi@vger.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 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.