linux-kernel - Re: [PATCH v9 2/4] dt-bindings: mtd: Add a property to declare secure regions in NAND chips

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210406163152.GA1919684@robh.at.kernel.org>
Date:   Tue, 6 Apr 2021 11:31:52 -0500
From:   Rob Herring <robh@...nel.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     Daniele.Palmas@...it.com, robh+dt@...nel.org,
        linux-arm-msm@...r.kernel.org, bjorn.andersson@...aro.org,
        boris.brezillon@...labora.com, devicetree@...r.kernel.org,
        vigneshr@...com, linux-mtd@...ts.infradead.org,
        miquel.raynal@...tlin.com, linux-kernel@...r.kernel.org,
        richard@....at
Subject: Re: [PATCH v9 2/4] dt-bindings: mtd: Add a property to declare
 secure regions in NAND chips

On Thu, 01 Apr 2021 20:45:06 +0530, Manivannan Sadhasivam wrote:
> On a typical end product, a vendor may choose to secure some regions in
> the NAND memory which are supposed to stay intact between FW upgrades.
> The access to those regions will be blocked by a secure element like
> Trustzone. So the normal world software like Linux kernel should not
> touch these regions (including reading).
> 
> So let's add a property for declaring such secure regions so that the
> drivers can skip touching them.
> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> ---
>  Documentation/devicetree/bindings/mtd/nand-controller.yaml | 7 +++++++
>  1 file changed, 7 insertions(+)
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.