From: "Laszlo Ersek" <lersek@redhat.com>
To: jejb@linux.ibm.com,
"Liming Gao (Byosoft address)" <gaoliming@byosoft.com.cn>
Cc: devel@edk2.groups.io, Bret Barkelew <brbarkel@microsoft.com>,
"Ard Biesheuvel (ARM address)" <ard.biesheuvel@arm.com>,
Hao A Wu <hao.a.wu@intel.com>,
Jian J Wang <jian.j.wang@intel.com>
Subject: Re: [PATCH] MdeModulePkg: Fix runtime panic in ValidateSetVariable()
Date: Wed, 25 Nov 2020 22:00:30 +0100 [thread overview]
Message-ID: <3090ce8d-74de-0fc7-985e-c4831091e478@redhat.com> (raw)
In-Reply-To: <414b7574bf8249de0cecd16fb422c711feb76e1a.camel@linux.ibm.com>
On 11/25/20 21:13, James Bottomley wrote:
> The current variable policy is allocated by AllocatePool(), which is
> boot time only. This means that if you do any variable setting in the
> runtime, the policy has been freed. Ordinarily this isn't detected
> because freed memory is still there, but when you boot the Linux
> kernel, it's been remapped so the actual memory no longer exists in
> the memory map causing a page fault.
>
> Fix this by making it AllocateRuntimePool(). For SMM drivers, the
> platform DSC is responsible for resolving the MemoryAllocationLib
> class to the SmmMemoryAllocationLib instance. In the
> SmmMemoryAllocationLib instance, AllocatePool() and
> AllocateRuntimePool() are implemented identically. Therefore this
> change is a no-op when the RegisterVariablePolicy() function is built
> into an SMM driver. The fix affects runtime DXE drivers only.
>
> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=3092
> Signed-off-by: James Bottomley <jejb@linux.ibm.com>
> ---
> MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c b/MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c
> index 5029ddb96adb..12944ac7ea81 100644
> --- a/MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c
> +++ b/MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c
> @@ -411,7 +411,7 @@ RegisterVariablePolicy (
> }
>
> // Reallocate and copy the table.
> - NewTable = AllocatePool( NewSize );
> + NewTable = AllocateRuntimePool( NewSize );
> if (NewTable == NULL) {
> return EFI_OUT_OF_RESOURCES;
> }
>
(1) CC'ing Jian and Hao:
$ python BaseTools/Scripts/GetMaintainer.py \
-l MdeModulePkg/Library/VariablePolicyLib/VariablePolicyLib.c
Jian J Wang <jian.j.wang@intel.com>
Hao A Wu <hao.a.wu@intel.com>
Liming Gao <gaoliming@byosoft.com.cn>
devel@edk2.groups.io
(2) My feedback:
Fixes: 355b181f74050cdf2f09b1755c1a5ee4affb1faf
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Tested-by: Laszlo Ersek <lersek@redhat.com>
(I tested the actual bugfix with SMM-less OVMF. I also
regression-tested the patch, namely with SMM OVMF, and ArmVirtQemu too.)
(3) I suggest updating the subject line as follows:
MdeModulePkg/VariablePolicyLib: Fix runtime panic in ValidateSetVariable()
74 characters, so it's not overlong.
No need to repost because of this.
Liming, can you please pick up my feedback tags from (2), in addition to
your own review, and refresh the subject as requested in (3), and then
merge this patch -- before releasing edk2-stable202011?
Thank you all,
Laszlo
next prev parent reply other threads:[~2020-11-25 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 20:13 [PATCH] MdeModulePkg: Fix runtime panic in ValidateSetVariable() James Bottomley
2020-11-25 21:00 ` Laszlo Ersek [this message]
2020-11-26 1:23 ` 回复: " gaoliming
[not found] ` <164AEA4706B9EEF6.8857@groups.io>
2020-11-27 0:58 ` 回复: [edk2-devel] " gaoliming
2020-11-25 21:05 ` Ard Biesheuvel
2020-11-25 21:17 ` Laszlo Ersek
2020-12-01 21:12 ` [EXTERNAL] Re: [edk2-devel] " Bret Barkelew
2020-12-03 10:39 ` Laszlo Ersek
2020-12-03 11:25 ` Ard Biesheuvel
2020-12-03 23:33 ` Laszlo Ersek
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=3090ce8d-74de-0fc7-985e-c4831091e478@redhat.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