linux-hardening - Re: [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the region dynamically

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 3 Feb 2023 13:50:34 +0530
From:   Mukesh Ojha <quic_mojha@...cinc.com>
To:     Rob Herring <robh@...nel.org>
CC:     <linux-hardening@...r.kernel.org>, <linux-doc@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <keescook@...omium.org>, <tony.luck@...el.com>,
        <gpiccoli@...lia.com>, <krzysztof.kozlowski+dt@...aro.org>,
        <corbet@....net>
Subject: Re: [PATCH v5 1/2] dt-bindings: ramoops: Add support to get the
 region dynamically



On 2/3/2023 5:29 AM, Rob Herring wrote:
> On Thu, Feb 02, 2023 at 02:58:00PM +0530, Mukesh Ojha wrote:
>> The reserved memory region for ramoops is assumed to be at a
>> fixed and known location when read from the devicetree. This
>> is not desirable in an environment where it is preferred the
>> region to be dynamically allocated at runtime, as opposed to
>> being fixed at compile time.
>>
>> So, update the ramoops binding by using some reserve memory
>> property to allocate the ramoops region dynamically.
> 
> Sorry, but I still don't think this belongs in DT as I commented on v4
Do you mean, we should not even document this here ? or are you against 
the size property mentioned in this patch.

-Mukesh