From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <mikuback@linux.microsoft.com>,
<osde@linux.microsoft.com>, <michael.d.kinney@intel.com>,
"'Leif Lindholm'" <leif.lindholm@oss.qualcomm.com>,
"'Ard Biesheuvel'" <ardb@kernel.org>,
"'Kubacki, Michael'" <michael.kubacki@microsoft.com>,
"'Andrew Fish'" <afish@apple.com>
Subject: 回复: [edk2-devel] Please Consider This PR for edk2-stable202505
Date: Thu, 22 May 2025 08:28:39 +0800 [thread overview]
Message-ID: <01a901dbcab0$79ed95f0$6dc8c1d0$@byosoft.com.cn> (raw)
In-Reply-To: <bfb5bc50-5bca-4a7a-81f5-4be96227805d@linux.microsoft.com>
OK. I will not merge it for this stable tag 202505.
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Michael
> Kubacki via groups.io
> 发送时间: 2025年5月21日 1:39
> 收件人: devel@edk2.groups.io; osde@linux.microsoft.com;
> michael.d.kinney@intel.com; gaoliming <gaoliming@byosoft.com.cn>; Leif
> Lindholm <leif.lindholm@oss.qualcomm.com>; Ard Biesheuvel
> <ardb@kernel.org>; Kubacki, Michael <michael.kubacki@microsoft.com>;
> Andrew Fish <afish@apple.com>
> 主题: Re: [edk2-devel] Please Consider This PR for edk2-stable202505
>
> I agree with postponing it until after the May stable tag.
>
> On 5/20/2025 1:30 PM, Oliver Smith-Denny via groups.io wrote:
> > On 5/20/2025 10:20 AM, Michael D Kinney via groups.io wrote:
> >> Hi Liming,
> >>
> >> +stewards
> >>
> >> It is still being reviewed. This is an important fix and needs to
> >> go in as soon as it is ready, but I do not think it should be considered
> >> for the stable tag. With the level of changes being discussed I would
> >> prefer it go in immediately after the stable tag and get lots of testing
> >> before the August stable tag.
> >>
> >
> > I agree with Mike. This is a longstanding issue that was just exposed
> > recently, but the fix has evolved into a riskier change that needs a lot
> > of testing.
> >
> > Released Linux shim versions with DebugClearMemory enabled will be
> > broken when loading certain Linux payloads without this change (and
> > there is a risk without DebugClearMemory enabled that pages would
> > get allocated to the next caller of AllocatePages set to RO and cause
> > unknown crashes). I defer to the stewards on the need to have this
> > stable tag contain a fix for this case or for it to get more testing
> > first (again, my preference).
> >
> > Thanks,
> > Oliver
> >
> >
> >
> >
> >
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121370): https://edk2.groups.io/g/devel/message/121370
Mute This Topic: https://groups.io/mt/113239781/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-05-22 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 16:25 [edk2-devel] Please Consider This PR for edk2-stable202505 Oliver Smith-Denny via groups.io
2025-05-20 1:05 ` 回复: " gaoliming via groups.io
2025-05-20 17:20 ` Michael D Kinney via groups.io
2025-05-20 17:30 ` Oliver Smith-Denny via groups.io
2025-05-20 17:39 ` Michael Kubacki via groups.io
2025-05-22 0:28 ` gaoliming via groups.io [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-list 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='01a901dbcab0$79ed95f0$6dc8c1d0$@byosoft.com.cn' \
--to=devel@edk2.groups.io \
/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