From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>,
Tom Rini <trini@konsulko.com>
Cc: Rick Chen <rick@andestech.com>, Bin Meng <bmeng.cn@gmail.com>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Sean Anderson <seanga2@gmail.com>,
Pragnesh Patel <pragnesh.patel@sifive.com>,
Zong Li <zong.li@sifive.com>,
Alexandre Ghiti <alexandre.ghiti@canonical.com>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: LMB and UEFI memory management not integrated.
Date: Thu, 11 Nov 2021 13:26:54 +0100 [thread overview]
Message-ID: <30dc41be-f583-f4e5-0693-0768017707b7@canonical.com> (raw)
In-Reply-To: <CAEn-LTrGpsLg_jdu=J8E0Ve+8M=KtRurxEHirigJq_sRbnKDfQ@mail.gmail.com>
>>>
>>> __lmb_alloc_base() seems not be integrated with the UEFI sub-system. So UEFI
>>> might hand out memory marked as reserved in the LMB sub-system.
>
> Heinrich, do you plan to work on this?
I am not sure if I will have enough capacity to work on the LMB/UEFI
integration. But it is surely an issue to be solved.
Best regards
Heinrich
>
> It would be great if we could finally solve this situation with the
> 2022.01 release.
>
> Right now Unmatched is probably the only board that doesn't turn off
> the relocation, and thus some people hit the issues.
>
> Looking at the git history, the LMB issue is fixed in v2022.01-rc1
> only right now. Minus UEFI part, which is/will be important for
> distributions.
>
> david
>
>>>
>>> I guess this is still a topic to be addressed.
>>
>> If UEFI can still end up getting U-Boot overwritten, yes, that needs to
>> be addressed. Only slightly surprised one of the capture-the-flag or
>> similar events hasn't come to us yet with some CVEs related to that,
>> too.
>>
>> --
>> Tom
next prev parent reply other threads:[~2021-11-11 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 14:45 [PATCH v2 0/2] board: sifive: unmatched: use zero copy for initrd Heinrich Schuchardt
2021-11-09 14:46 ` [PATCH v2 1/2] " Heinrich Schuchardt
2021-11-09 15:46 ` Tom Rini
2021-11-09 15:50 ` Heinrich Schuchardt
2021-11-09 16:07 ` Tom Rini
2021-11-09 16:27 ` Heinrich Schuchardt
2021-11-09 17:11 ` Tom Rini
2021-11-11 9:46 ` David Abdurachmanov
2021-11-11 12:26 ` Heinrich Schuchardt [this message]
2021-11-09 14:46 ` [PATCH v2 2/2] board: sifive: unmatched: rearrange load addresses Heinrich Schuchardt
2021-11-09 15:43 ` Tom Rini
2021-11-09 15:46 ` Heinrich Schuchardt
2021-11-09 15:48 ` 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=30dc41be-f583-f4e5-0693-0768017707b7@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=alexandre.ghiti@canonical.com \
--cc=bmeng.cn@gmail.com \
--cc=david.abdurachmanov@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=pragnesh.patel@sifive.com \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
--cc=zong.li@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.