public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Baskov Evgeniy <baskov@ispras.ru>, Ingo Molnar <mingo@kernel.org>,
	Radek Podgorny <radek@podgorny.cz>,
	linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	linux-hardening@vger.kernel.org
Subject: [PATCH v2 0/2] efi: Replace efi_memory_attributes_table_t 0-sized array with flexible array
Date: Thu, 11 Jul 2024 10:11:11 -0700	[thread overview]
Message-ID: <20240711170727.it.194-kees@kernel.org> (raw)

Hi,

Update efi_memory_attributes_table_t to use a proper flexible
array. Renames efi_early_memdesc_ptr() to efi_memdesc_ptr() so it more
accurately reflects its usage.

Thanks!

-Kees

 v2:
  - rename efi_early_memdesc_ptr() to efi_memdesc_ptr()
  - add comment about reading efi_memdesc_ptr() to efi_memory_attributes_table_t
 v1: https://lore.kernel.org/lkml/20240710225538.work.224-kees@kernel.org/

Kees Cook (2):
  efi: Rename efi_early_memdesc_ptr() to efi_memdesc_ptr()
  efi: Replace efi_memory_attributes_table_t 0-sized array with flexible
    array

 drivers/firmware/efi/libstub/relocate.c          |  2 +-
 drivers/firmware/efi/libstub/unaccepted_memory.c |  2 +-
 drivers/firmware/efi/libstub/x86-stub.c          |  2 +-
 drivers/firmware/efi/memattr.c                   |  2 +-
 include/linux/efi.h                              | 10 +++++++---
 5 files changed, 11 insertions(+), 7 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-07-11 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11 17:11 Kees Cook [this message]
2024-07-11 17:11 ` [PATCH v2 1/2] efi: Rename efi_early_memdesc_ptr() to efi_memdesc_ptr() Kees Cook
2024-07-11 17:11 ` [PATCH v2 2/2] efi: Replace efi_memory_attributes_table_t 0-sized array with flexible array Kees Cook
2024-07-12  8:08 ` [PATCH v2 0/2] " Ard Biesheuvel

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=20240711170727.it.194-kees@kernel.org \
    --to=kees@kernel.org \
    --cc=ardb@kernel.org \
    --cc=baskov@ispras.ru \
    --cc=bp@alien8.de \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=radek@podgorny.cz \
    /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