From: Usama Arif <usamaarif642@gmail.com>
To: Gregory Price <gourry@gourry.net>, linux-efi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ardb@kernel.org
Subject: Re: [PATCH 2/2] tpm: do not ignore memblock_reserve return value
Date: Fri, 30 Aug 2024 22:33:22 +0100 [thread overview]
Message-ID: <3f79211f-f82c-4e41-9b40-e0abcbb4bdf0@gmail.com> (raw)
In-Reply-To: <20240830132303.6665-2-gourry@gourry.net>
On 30/08/2024 09:23, Gregory Price wrote:
> tpm code currently ignores a relevant failure case silently.
> Add an error to make this failure non-silent.
>
> Signed-off-by: Gregory Price <gourry@gourry.net>
> ---
> drivers/firmware/efi/tpm.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/efi/tpm.c b/drivers/firmware/efi/tpm.c
> index 9c3613e6af15..b6939a6d44d9 100644
> --- a/drivers/firmware/efi/tpm.c
> +++ b/drivers/firmware/efi/tpm.c
> @@ -61,7 +61,11 @@ int __init efi_tpm_eventlog_init(void)
> }
>
> tbl_size = sizeof(*log_tbl) + log_tbl->size;
> - memblock_reserve(efi.tpm_log, tbl_size);
> + if (memblock_reserve(efi.tpm_log, tbl_size)) {
> + pr_err("TPM Event Log memblock reserve fails 0x%lx - %x\n",
> + efi.tpm_log, tbl_size);
> + goto out;
> + }
>
> if (efi.tpm_final_log == EFI_INVALID_TABLE_ADDR) {
> pr_info("TPM Final Events table not present\n");
This was not a proper fix for the issue, sent a bit quickly!
I have sent it here https://lore.kernel.org/all/20240830212852.2794145-1-usamaarif642@gmail.com/
next prev parent reply other threads:[~2024-08-30 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:23 [PATCH 1/2] tpm: fix signed/unsigned bug when checking event logs Gregory Price
2024-08-30 13:23 ` [PATCH 2/2] tpm: do not ignore memblock_reserve return value Gregory Price
2024-08-30 21:33 ` Usama Arif [this message]
2024-08-30 21:44 ` Gregory Price
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=3f79211f-f82c-4e41-9b40-e0abcbb4bdf0@gmail.com \
--to=usamaarif642@gmail.com \
--cc=ardb@kernel.org \
--cc=gourry@gourry.net \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox