From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] efi_selftest: check length report by GetNextVariableName()
Date: Mon, 30 Mar 2020 15:43:26 +0900 [thread overview]
Message-ID: <20200330064325.GB11504@linaro.org> (raw)
In-Reply-To: <20200320182820.149823-3-xypron.glpk@gmx.de>
On Fri, Mar 20, 2020 at 07:28:20PM +0100, Heinrich Schuchardt wrote:
> GetNextVariableName should report the length of the variable including the
> final 0x0000 in bytes.
>
> Check this in the unit test.
>
> Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> lib/efi_selftest/efi_selftest_variables.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/lib/efi_selftest/efi_selftest_variables.c b/lib/efi_selftest/efi_selftest_variables.c
> index 5d98c029b8..b7ead340f5 100644
> --- a/lib/efi_selftest/efi_selftest_variables.c
> +++ b/lib/efi_selftest/efi_selftest_variables.c
> @@ -155,8 +155,14 @@ static int execute(void)
> return EFI_ST_FAILURE;
> }
> if (!memcmp(&guid, &guid_vendor0, sizeof(efi_guid_t)) &&
> - !efi_st_strcmp_16_8(varname, "efi_st_var0"))
> + !efi_st_strcmp_16_8(varname, "efi_st_var0")) {
> flag |= 1;
> + if (len != 24) {
> + efi_st_error("GetNextVariableName report wrong length %u, expected 24\n",
> + (unsigned int)len);
> + return EFI_ST_FAILURE;
> + }
> + }
> if (!memcmp(&guid, &guid_vendor1, sizeof(efi_guid_t)) &&
> !efi_st_strcmp_16_8(varname, "efi_st_var1"))
Logically, length check should be added here, too.
-Takahiro Akashi
> flag |= 2;
> --
> 2.25.1
>
prev parent reply other threads:[~2020-03-30 6:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 18:28 [PATCH 0/2] efi_loader: correct reported length in GetNextVariable() Heinrich Schuchardt
2020-03-20 18:28 ` [PATCH 1/2] " Heinrich Schuchardt
2020-03-24 8:41 ` Punit Agrawal
2020-03-30 6:40 ` AKASHI Takahiro
2020-03-20 18:28 ` [PATCH 2/2] efi_selftest: check length report by GetNextVariableName() Heinrich Schuchardt
2020-03-30 6:43 ` AKASHI Takahiro [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=20200330064325.GB11504@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=u-boot@lists.denx.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