From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Isaac J. Manjarres" <isaacmanjarres@google.com>,
Kees Cook <keescook@chromium.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Rob Herring <robh+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "Isaac J. Manjarres" <isaacm@codeaurora.org>,
Mukesh Ojha <mojha@codeaurora.org>,
Prasad Sodagudi <psodagud@codeaurora.org>,
kernel-team@android.com, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pstore/ram: Add support for dynamically allocated ramoops memory regions
Date: Tue, 4 Jul 2023 08:05:21 +0200 [thread overview]
Message-ID: <946f9db2-41a0-b58c-771a-5a82fdf28039@kernel.org> (raw)
In-Reply-To: <20230622005213.458236-1-isaacmanjarres@google.com>
On 22/06/2023 02:52, Isaac J. Manjarres wrote:
> From: "Isaac J. Manjarres" <isaacm@codeaurora.org>
>
> 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 environments where it is preferred for the region to be dynamically
> allocated early during boot (i.e. the memory region is defined with
> the "alloc-ranges" property instead of the "reg" property).
>
> If the location of the ramoops region is not fixed via the "reg"
> devicetree property, the call to platform_get_resource() will fail
> because resources of type IORESOURCE_MEM must be described with the
> "reg" property.
>
> Since ramoops regions are part of the reserved-memory devicetree
> node, they exist in the reserved_mem array. This means that the
> of_reserved_mem_lookup() function can be used to retrieve the
> reserved_mem structure for the ramoops region, and that structure
> contains the base and size of the region, even if it has been
> dynamically allocated.
>
> Thus invoke of_reserved_mem_lookup() in case the call to
> platform_get_resource() fails in order to support dynamically
> allocated ramoops memory regions.
You missed change to Devicetree binding, so the reg is still required
for all DT-based platforms. For such, this patch is just half-baked.
You also did not CC DT maintainers, which would be nice considering some
improper advises for minidump like here:
https://lore.kernel.org/lkml/e25723bf-be85-b458-a84c-1a45392683bb@gmail.com/
DT is not for some dynamically allocated properties or dynamic system
configuration. You don't need DT for that. Therefore if you remove the
reg, I question the entire point of this binding.
See also:
https://lore.kernel.org/lkml/CAL_JsqJ_TTnGjjB2d8_FKHpWBRG5GHLoWnabCKjsdeZ4QFdNEg@mail.gmail.com/
https://lore.kernel.org/lkml/20230202235916.GA2931100-robh@kernel.org/
Best regards,
Krzysztof
prev parent reply other threads:[~2023-07-04 6:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:52 Isaac J. Manjarres
2023-06-22 4:47 ` John Stultz
2023-06-22 5:15 ` Kees Cook
2023-06-22 17:26 ` Isaac Manjarres
2023-06-22 17:58 ` Kees Cook
2023-06-22 19:51 ` Elliot Berman
2023-06-26 17:34 ` Mukesh Ojha
2023-07-04 6:07 ` Krzysztof Kozlowski
2023-07-05 22:21 ` Kees Cook
2023-07-06 16:00 ` Mukesh Ojha
2023-07-04 6:05 ` Krzysztof Kozlowski
2023-06-22 17:19 ` Isaac Manjarres
2023-07-04 6:05 ` Krzysztof Kozlowski [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=946f9db2-41a0-b58c-771a-5a82fdf28039@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=isaacm@codeaurora.org \
--cc=isaacmanjarres@google.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mojha@codeaurora.org \
--cc=psodagud@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®