From: Krzysztof Kozlowski <krzk@kernel.org>
To: Elliot Berman <quic_eberman@quicinc.com>,
Kees Cook <kees@kernel.org>,
Isaac Manjarres <isaacmanjarres@google.com>,
Kees Cook <keescook@chromium.org>
Cc: John Stultz <jstultz@google.com>, Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
kernel-team@android.com, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org,
Trilok Soni <quic_tsoni@quicinc.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@quicinc.com>,
Mukesh Ojha <quic_mojha@quicinc.com>
Subject: Re: [PATCH] pstore/ram: Add support for dynamically allocated ramoops memory regions
Date: Tue, 4 Jul 2023 08:05:08 +0200 [thread overview]
Message-ID: <3fde3786-24c8-1a03-bd35-5f83ee3474ba@kernel.org> (raw)
In-Reply-To: <a2c9417b-3a50-bea4-dd39-2f021c196fa1@quicinc.com>
On 22/06/2023 21:51, Elliot Berman wrote:
>> Boot 1.
>> Get address Foo.
>> Crash, write to Foo.
>> Boot 2.
>> Get address Bar, different from Foo.
>> Nothing found at Bar, so nothing populated in pstorefs; crash report from Boot 1 unavailable.
>>
>> I feel like there is something I don't understand about the Foo/Bar addresses in my example.
>>
>
> I believe this is being added to support the QCOM SoC minidump feature.
> Mukesh has posted it on the mailing lists here:
>
> https://lore.kernel.org/all/1683133352-10046-1-git-send-email-quic_mojha@quicinc.com/
>
> https://lore.kernel.org/all/1683133352-10046-10-git-send-email-quic_mojha@quicinc.com/
And since this is coming bypassing DT maintainers and clearly against
Rob's feedback so far, that's a no.
>
> Mukesh, could you comment whether this patch is wanted for us in the
> version you have posted? It looks like maybe not based on the commit
> text in patch #9.
Best regards,
Krzysztof
next 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 [PATCH] pstore/ram: Add support for dynamically allocated ramoops memory regions 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 [this message]
2023-06-22 17:19 ` Isaac Manjarres
2023-07-04 6:05 ` Krzysztof Kozlowski
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=3fde3786-24c8-1a03-bd35-5f83ee3474ba@kernel.org \
--to=krzk@kernel.org \
--cc=gpiccoli@igalia.com \
--cc=isaacmanjarres@google.com \
--cc=jstultz@google.com \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_eberman@quicinc.com \
--cc=quic_mojha@quicinc.com \
--cc=quic_satyap@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--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