All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>
Cc: Dan Williams <djbw@kernel.org>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>, Ira Weiny <iweiny@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, Jeff Moyer <jmoyer@redhat.com>,
	Ross Zwisler <zwisler@kernel.org>, <nvdimm@lists.linux.dev>,
	<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/5] ACPI: NFIT: harden subtable extent validation
Date: Thu, 13 Aug 2026 15:51:38 -0700	[thread overview]
Message-ID: <an5KepVGGITAfr2M@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260813150948.17239-1-pengpeng@iscas.ac.cn>

On Thu, Aug 13, 2026 at 11:09:48PM +0800, Pengpeng Hou wrote:
> NFIT parsing has several independent extent contracts: the outer table
> must contain each advertised subtable, and variable or versioned records
> must fit inside that subtable.  The original patch mixed those contracts
> and also derived the SPA structure length from the location-cookie-valid
> flag.
> 
> Split the checks by record type.  Patch 1 validates the generic subtable
> header and outer extent.  Patch 2 accepts both defined SPA layouts while
> treating the cookie flag as a validity bit, not a size selector.  Patches
> 3 and 4 validate the variable arrays and the control-region extent.
> Patch 5 bounds the 32-bit capability mask without rejecting future
> firmware that advertises a higher capability index.
> 
> Changes since v1:
> https://lore.kernel.org/all/20260722041701.21078-1-pengpeng@iscas.ac.cn/

NAK
See: Documentation/process/submitting-patches.rst 
Section "Respond to review comments"


> - split the generic and type-specific contracts into separate patches
> - handle both 56-byte and 64-byte SPA structures
> - add the control-region extent check identified during review
> - clamp the implemented capability mask instead of rejecting future bits
> - describe the exact fields protected by each check
> 
> The series was reviewed statically against the current tree. I did not
> run an NFIT firmware fault-injection test.
> 
> Pengpeng Hou (5):
>   ACPI: NFIT: validate subtable extents before dispatch
>   ACPI: NFIT: accept SPA structures with an unused location cookie
>   ACPI: NFIT: validate interleave and flush array extents
>   ACPI: NFIT: validate control region extent
>   ACPI: NFIT: bound the platform capability mask
> 
>  drivers/acpi/nfit/core.c | 77 ++++++++++++++++++++++++++++++++--------
>  1 file changed, 62 insertions(+), 15 deletions(-)
> 
> base-commit: f5bbbfec59b4e2fb7520a91de3df8a6174325d6a
> 
> -- 
> 2.50.1 (Apple Git-155)
> 

      parent reply	other threads:[~2026-08-13 22:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 15:09 [PATCH v2 0/5] ACPI: NFIT: harden subtable extent validation Pengpeng Hou
2026-08-13 15:11 ` [PATCH v2 1/5] ACPI: NFIT: validate subtable extents before dispatch Pengpeng Hou
2026-08-13 15:41   ` sashiko-bot
2026-08-13 15:13 ` [PATCH v2 2/5] ACPI: NFIT: accept SPA structures with an unused location cookie Pengpeng Hou
2026-08-13 15:35   ` sashiko-bot
2026-08-13 15:16 ` [PATCH v2 3/5] ACPI: NFIT: validate interleave and flush array extents Pengpeng Hou
2026-08-13 15:38   ` sashiko-bot
2026-08-13 15:18 ` [PATCH v2 4/5] ACPI: NFIT: validate control region extent Pengpeng Hou
2026-08-13 15:38   ` sashiko-bot
2026-08-13 15:20 ` [PATCH v2 5/5] ACPI: NFIT: bound the platform capability mask Pengpeng Hou
2026-08-13 15:33   ` sashiko-bot
2026-08-13 22:51 ` Alison Schofield [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=an5KepVGGITAfr2M@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=djbw@kernel.org \
    --cc=iweiny@kernel.org \
    --cc=jmoyer@redhat.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=pengpeng@iscas.ac.cn \
    --cc=rafael@kernel.org \
    --cc=vishal.l.verma@intel.com \
    --cc=zwisler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.