public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Oliver Smith-Denny via groups.io" <osde=linux.microsoft.com@groups.io>
To: devel@edk2.groups.io, 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>
Subject: Re: [edk2-devel] Please Consider This PR for edk2-stable202505
Date: Tue, 20 May 2025 10:30:51 -0700	[thread overview]
Message-ID: <1d0f4e1e-94c5-49cf-bc0b-da9172f1238a@linux.microsoft.com> (raw)
In-Reply-To: <CO1PR11MB492973919752BC2DE8670AC0D29FA@CO1PR11MB4929.namprd11.prod.outlook.com>

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 (#121363): https://edk2.groups.io/g/devel/message/121363
Mute This Topic: https://groups.io/mt/113215139/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2025-05-20 17:30 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 [this message]
2025-05-20 17:39       ` Michael Kubacki via groups.io
2025-05-22  0:28         ` 回复: " gaoliming via groups.io

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=1d0f4e1e-94c5-49cf-bc0b-da9172f1238a@linux.microsoft.com \
    --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