From: Rob Herring <robh@kernel.org>
To: Lucas Tanure <tanure@linux.com>
Cc: linux-arm-kernel@lists.infradead.org, narmstrong@baylibre.com,
devicetree@vger.kernel.org, Mike Rapoport <rppt@kernel.org>,
martin.blumenstingl@googlemail.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-amlogic@lists.infradead.org,
Frank Rowand <frowand.list@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
jbrunet@baylibre.com, stefan@agner.ch,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] of: fdt: Scan /memreserve/ last
Date: Thu, 27 Apr 2023 16:04:17 -0500 [thread overview]
Message-ID: <168262872454.3491083.6407810340850053636.robh@kernel.org> (raw)
In-Reply-To: <20230424113846.46382-1-tanure@linux.com>
On Mon, 24 Apr 2023 12:38:46 +0100, Lucas Tanure wrote:
> Change the scanning /memreserve/ and /reserved-memory node order to fix
> Kernel panic on Khadas Vim3 Board.
>
> If /memreserve/ goes first, the memory is reserved, but nomap can't be
> applied to the region. So the memory won't be used by Linux, but it is
> still present in the linear map as normal memory, which allows
> speculation. Legitimate access to adjacent pages will cause the CPU
> to end up prefetching into them leading to Kernel panic.
>
> So /reserved-memory node should go first, as it has a more updated
> description of the memory regions and can apply flags, like nomap.
>
> Signed-off-by: Lucas Tanure <tanure@linux.com>i
> ---
> Previous Threads:
> #regzbot link: https://lore.kernel.org/linux-arm-kernel/40ca11f84b7cdbfb9ad2ddd480cb204a@agner.ch/#regzbot
> #regzbot link: https://lore.kernel.org/all/CAJX_Q+1Tjc+-TjZ6JW9X0NxEdFe=82a9626yL63j7uVD4LpxEA@mail.gmail.com/
Note that this should have been a 'Link:' entry in the commit message
for regzbot. I added it.
>
> V1: https://lore.kernel.org/all/20230406151429.524591-1-tanure@linux.com/
> v2: https://lore.kernel.org/all/20230410120017.41664-1-tanure@linux.com/
> v3: https://lore.kernel.org/linux-mm/20230412224620.8909-1-tanure@linux.com/T/
>
> Change from V3:
> - Drop cover letter
> - Add more information into the patch
>
> Change from V2:
> - Remove region overlap and reserved checks
>
> Change from V1:
> - Instead of allowing to mark nomap a region already reserved, give
> precedence to /reserved-memory node scan.
> ---
> drivers/of/fdt.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
Applied, thanks!
Going to let this sit in linux-next for a bit. I also didn't tag for
stable kernels. I want it to get some exposure in mainline at least for
a few -rc releases rather than getting backported right away. Please
help ensure that happens if you see stable review emails. I'm going to
be offline most of the next month.
Rob
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2023-04-27 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 11:38 Lucas Tanure
2023-04-27 21:04 ` Rob Herring [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=168262872454.3491083.6407810340850053636.robh@kernel.org \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=rppt@kernel.org \
--cc=stefan@agner.ch \
--cc=tanure@linux.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®