From: "Michael D Kinney via groups.io" <michael.d.kinney=intel.com@groups.io>
To: gaoliming <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"osde@linux.microsoft.com" <osde@linux.microsoft.com>,
Leif Lindholm <leif.lindholm@oss.qualcomm.com>,
Ard Biesheuvel <ardb@kernel.org>,
"Kubacki, Michael" <michael.kubacki@microsoft.com>,
Andrew Fish <afish@apple.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Please Consider This PR for edk2-stable202505
Date: Tue, 20 May 2025 17:20:53 +0000 [thread overview]
Message-ID: <CO1PR11MB492973919752BC2DE8670AC0D29FA@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <000001dbc923$4ffc3a50$eff4aef0$@byosoft.com.cn>
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.
Mike
> -----Original Message-----
> From: gaoliming <gaoliming@byosoft.com.cn>
> Sent: Monday, May 19, 2025 6:06 PM
> To: devel@edk2.groups.io; osde@linux.microsoft.com; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: 回复: [edk2-devel] Please Consider This PR for edk2-stable202505
>
> I see this PR is still under discussion. Does it finalize?
>
> > -----邮件原件-----
> > 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Oliver
> > Smith-Denny via groups.io
> > 发送时间: 2025年5月17日 0:25
> > 收件人: devel@edk2.groups.io; Liming Gao <gaoliming@byosoft.com.cn>;
> > Michael Kinney <michael.d.kinney@intel.com>
> > 主题: [edk2-devel] Please Consider This PR for edk2-stable202505
> >
> > Hi Liming and Mike,
> >
> > This PR https://github.com/tianocore/edk2/pull/11086
> > addresses a crash for the Linux shim v16 on debug
> > builds. When DebugClearMemory is set, DXE Core will
> > currently attempt to write to all freed pages, even
> > if they are not writeable. This patch ensures that
> > DXE Core will change the memory attributes of
> > the free pages before writing to them, or will
> > not write to them if it fails to.
> >
> > Without this, users of shim v16 will experience
> > failures when using builds of edk2 that have
> > DebugClearMemory set when loading certain
> > Linux distributions. Please consider merging
> > this for edk2-stable202505.
> >
> > Thanks,
> > Oliver
> >
> >
> >
> >
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121362): https://edk2.groups.io/g/devel/message/121362
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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2025-05-20 17:21 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 [this message]
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
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=CO1PR11MB492973919752BC2DE8670AC0D29FA@CO1PR11MB4929.namprd11.prod.outlook.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