From: Tom Rini <trini@konsulko.com>
To: Marek Vasut <marex@denx.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Wolfgang Denk <wd@denx.de>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Hai Pham <hai.pham.ud@renesas.com>,
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>,
Stephen Warren <swarren@nvidia.com>,
Lokesh Vutla <lokeshvutla@ti.com>, Ye Li <ye.li@nxp.com>
Subject: Re: [PATCH] Revert "arm: bootm: Disable LMB reservation for command line and board info on arm64"
Date: Sun, 8 Aug 2021 11:57:53 -0400 [thread overview]
Message-ID: <20210808155753.GJ858@bill-the-cat> (raw)
In-Reply-To: <9dbf9adb-7f6b-4b3c-859a-9a0024c69917@denx.de>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Sun, Aug 08, 2021 at 05:25:33PM +0200, Marek Vasut wrote:
> On 8/8/21 4:54 PM, Tom Rini wrote:
>
> [...]
>
> > > > I expect it was not simply because up
> > > > until rather recently we didn't have any checks for "don't overwrite
> > > > specific areas of memory" other than right before firing off the OS (and
> > > > modify whatever memory you want to modify is a feature not a bug).
> > >
> > > The LMB has been around since forever though ?
> >
> > Yes, LMB has been around since the PowerPC device tree days I suspect (I
> > didn't dig that far back), but only used outside of the "don't overwrite
> > the running U-Boot while we relocate device tree / initrd before booting
> > OS" since 2018 or so.
>
> So, are we using LMB for two different things now ?
For "now" == "2.5 years", yes, we've used the "LMB stops us from
overwriting running U-Boot" as part of addressing the CVEs I quoted.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-08-08 15:58 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 7:22 [PATCH] Revert "arm: bootm: Disable LMB reservation for command line and board info on arm64" Jan Kiszka
2021-07-29 15:01 ` Marek Vasut
2021-07-29 15:23 ` Tom Rini
2021-07-29 16:47 ` Marek Vasut
2021-07-29 16:58 ` Tom Rini
2021-08-02 0:54 ` Marek Vasut
2021-08-02 9:37 ` Jan Kiszka
2021-08-02 10:48 ` Marek Vasut
2021-08-02 11:36 ` Jan Kiszka
2021-08-02 11:38 ` Marek Vasut
2021-08-02 11:54 ` Jan Kiszka
2021-08-02 13:04 ` Tom Rini
2021-08-02 14:03 ` Jan Kiszka
2021-08-02 14:27 ` Tom Rini
2021-08-02 14:34 ` Jan Kiszka
2021-08-02 14:44 ` Tom Rini
2021-08-05 21:52 ` Marek Vasut
2021-08-06 16:43 ` Tom Rini
2021-08-02 13:00 ` Tom Rini
2021-08-05 21:53 ` Marek Vasut
2021-08-05 23:31 ` Tom Rini
2021-08-08 13:35 ` Marek Vasut
2021-08-02 21:27 ` Tom Rini
2021-08-03 21:51 ` Tom Rini
2021-08-05 22:22 ` Marek Vasut
2021-08-06 16:49 ` Tom Rini
2021-08-08 13:45 ` Marek Vasut
2021-08-08 14:00 ` Tom Rini
2021-08-08 14:28 ` Marek Vasut
2021-08-08 14:54 ` Tom Rini
2021-08-08 15:25 ` Marek Vasut
2021-08-08 15:57 ` Tom Rini [this message]
2021-08-09 7:34 ` [EXT] " Ye Li
2021-08-09 13:16 ` Tom Rini
2021-08-09 14:11 ` Wolfgang Denk
2021-08-09 14:21 ` Tom Rini
2021-08-09 6:44 ` Wolfgang Denk
2021-08-09 12:53 ` Tom Rini
2021-08-08 18:21 ` Tom Rini
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=20210808155753.GJ858@bill-the-cat \
--to=trini@konsulko.com \
--cc=hai.pham.ud@renesas.com \
--cc=jan.kiszka@siemens.com \
--cc=lokeshvutla@ti.com \
--cc=marex@denx.de \
--cc=simon.k.r.goldschmidt@gmail.com \
--cc=swarren@nvidia.com \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
--cc=ye.li@nxp.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