From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Michal Simek <michal.simek@amd.com>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
u-boot@lists.denx.de, git@xilinx.com
Subject: Re: [PATCH] efi_loader: Allow also empty capsule to be process
Date: Thu, 27 Jul 2023 09:46:35 +0900 [thread overview]
Message-ID: <ZMG-a0Y9x7LuCe4B@laputa> (raw)
In-Reply-To: <085a575a-f1f8-b2b9-762a-e9a25246b557@amd.com>
Hi Michal, Sughosh,
On Wed, Jul 26, 2023 at 06:36:56PM +0200, Michal Simek wrote:
>
>
> On 7/26/23 15:07, Ilias Apalodimas wrote:
> > Hi all
> >
> > [...]
> >
> > > > >
> > > >
> > > > Hello Sugosh,
> > > >
> > > > fwu_empty_capsule() detects an empty capsule as one with a GUID
> > > > fwu_guid_os_request_fw_revert or fwu_guid_os_request_fw_accept.
> > > >
> > > > I am not aware of a requirement in the UEFI specification to treat
> > > > capsules read from file in a different way than capsules passed via
> > > > UpdateCapsule(). Is there any reason why UpdateCapsule() should not
> > > > process an empty capsule when called from a boot-time EFI application?
> > >
> > > Here is a story behind efi_update_capsule():
> > > ===
> > > commit a6aafce494ab
> > > Author: Masami Hiramatsu <masami.hiramatsu@linaro.org>
> > > Date: Wed Feb 16 15:15:42 2022 +0900
> > >
> > > efi_loader: use efi_update_capsule_firmware() for capsule on disk
> > > ===
> > >
> > > I still believe that this is a valid change, but we should have
> > > moved 'capsule->capsule_guid' check into efi_update_capsule_firmware()
> > > at the same time.
> >
> > I agree with Akashi-san here. I am also fine with this patchset since
> > running the A/B update from an EFI app should work. But can we do a v2
> > with 2 patches?
> > #1 move the capsule check along with the empty capsule checks in
> > efi_update_capsule_firmware()
> > #2 fix the a/b updates via the runtime calls and adjust the commit
> > message accordingly, explaining why this change is needed?
>
> Can someone from Linaro create v2 on this?
> I just wanted to pointed to it.
Yes, I posted "efi_loader: capsule: enforce guid check in api and
capsule_on_disk".
Since I didn't run any test against A/B update, can you please
confirm that this patch works in your environment?
Unlike Ilias suggested, I made a single patch because an empty
capsule will be handled any way at the beginning of
efi_capsule_update_firmware() and we process only normal capsules
after that.
-Takahiro Akashi
> Thanks,
> Michal
next prev parent reply other threads:[~2023-07-27 0:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 14:35 [PATCH] efi_loader: Allow also empty capsule to be process Michal Simek
2023-07-18 15:41 ` Heinrich Schuchardt
2023-07-19 6:28 ` Michal Simek
2023-07-20 5:49 ` AKASHI Takahiro
2023-07-20 6:07 ` Michal Simek
2023-07-20 6:36 ` Sughosh Ganu
2023-07-20 7:56 ` Michal Simek
2023-07-20 8:45 ` Sughosh Ganu
2023-07-20 9:26 ` Michal Simek
2023-07-20 9:48 ` Sughosh Ganu
2023-07-20 20:42 ` Heinrich Schuchardt
2023-07-21 4:48 ` AKASHI Takahiro
2023-07-26 13:07 ` Ilias Apalodimas
2023-07-26 16:36 ` Michal Simek
2023-07-27 0:46 ` AKASHI Takahiro [this message]
2023-07-26 12:54 ` Ilias Apalodimas
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=ZMG-a0Y9x7LuCe4B@laputa \
--to=takahiro.akashi@linaro.org \
--cc=git@xilinx.com \
--cc=ilias.apalodimas@linaro.org \
--cc=michal.simek@amd.com \
--cc=sughosh.ganu@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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