From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ard Biesheuvel <ardb@kernel.org>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Sumit Garg <sumit.garg@linaro.org>,
Jens Wiklander <jens.wiklander@linaro.org>
Subject: [PATCH 0/3] efi: stmm: Fix for incorrect buffer allocation and cleanups
Date: Fri, 15 Aug 2025 21:12:38 +0200 [thread overview]
Message-ID: <cover.1755285161.git.jan.kiszka@siemens.com> (raw)
One critical fix for the EFI StMM driver and two smaller cleanups.
I'm carefully optimistic that we will get better test coverage in the
future: I have a working RPMB model for QEMU, and this is where the
crash was found now and debugged in.
Jan
Jan Kiszka (3):
efi: stmm: Fix incorrect buffer allocation method
efi: stmm: Use EFI return code of setup_mm_hdr
efi: stmm: Drop unneeded null pointer check
drivers/firmware/efi/stmm/tee_stmm_efi.c | 59 ++++++++++++++----------
1 file changed, 34 insertions(+), 25 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-15 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 19:12 Jan Kiszka [this message]
2025-08-15 19:12 ` [PATCH 1/3] efi: stmm: Fix incorrect buffer allocation method Jan Kiszka
2025-08-20 7:29 ` Ilias Apalodimas
2025-08-20 15:05 ` Jan Kiszka
2025-08-21 9:35 ` Sumit Garg
2025-08-21 12:56 ` Jan Kiszka
2025-08-22 9:07 ` Sumit Garg
2025-08-15 19:12 ` [PATCH 2/3] efi: stmm: Use EFI return code of setup_mm_hdr Jan Kiszka
2025-08-20 7:10 ` Ilias Apalodimas
2025-08-20 14:59 ` Jan Kiszka
2025-08-21 13:00 ` Jan Kiszka
2025-08-21 13:26 ` Ilias Apalodimas
2025-08-15 19:12 ` [PATCH 3/3] efi: stmm: Drop unneeded null pointer check Jan Kiszka
2025-08-20 6:44 ` 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=cover.1755285161.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ardb@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahisa.kojima@linaro.org \
--cc=sumit.garg@linaro.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;
as well as URLs for NNTP newsgroup(s).