From: "Kubacki, Michael A" <michael.a.kubacki@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>
Subject: Re: [edk2-devel] [PATCH V1 1/1] MdeModulePkg/Variable: Fix volatile variable RT cache update logic
Date: Mon, 11 Nov 2019 06:11:17 +0000 [thread overview]
Message-ID: <BY5PR11MB4484BDF21F4DD0E382A8953FB5740@BY5PR11MB4484.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E53C580@SHSMSX104.ccr.corp.intel.com>
After a new volatile variable is written successfully, Runtime Services GetVariable () may return
EFI_NOT_FOUND for that variable.
Thanks,
Michael
> -----Original Message-----
> From: Gao, Liming <liming.gao@intel.com>
> Sent: Sunday, November 10, 2019 10:08 PM
> To: devel@edk2.groups.io; Kubacki, Michael A
> <michael.a.kubacki@intel.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Wang, Jian J
> <jian.j.wang@intel.com>; Wu, Hao A <hao.a.wu@intel.com>; Gao, Liming
> <liming.gao@intel.com>
> Subject: RE: [edk2-devel] [PATCH V1 1/1] MdeModulePkg/Variable: Fix
> volatile variable RT cache update logic
>
> Michael:
> What real issue is caused by this issue?
>
> Thanks
> Liming
> >-----Original Message-----
> >From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> >Kubacki, Michael A
> >Sent: Monday, November 11, 2019 1:16 PM
> >To: devel@edk2.groups.io
> >Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
> ><michael.d.kinney@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Wu,
> >Hao A <hao.a.wu@intel.com>
> >Subject: [edk2-devel] [PATCH V1 1/1] MdeModulePkg/Variable: Fix
> >volatile variable RT cache update logic
> >
> >REF:https://bugzilla.tianocore.org/show_bug.cgi?id=2333
> >
> >During a SetVariable () invocation, UpdateVariable () is called.
> >UpdateVariable () contains logic to determine whether a volatile or
> >non-volatile UEFI variable was set so the corresponding runtime cache
> >can be updated to reflect the change. The current logic simply
> >evaluates Variable->Volatile to determine which runtime cache should be
> >updated.
> >
> >The problem is Variable->Volatile does not always reflect whether a
> >volatile variable is being set. Variable->Volatile is set to TRUE only
> >in the case a pre-existing variable is found in the volatile variable
> >store. Therefore, the value is FALSE when a new volatile variable is
> >written.
> >
> >This change updates the logic to take this into account. If a new
> >variable is written successfully, the Attributes will accurately
> >reflect whether the variable is non-volatile. If a pre-existing
> >variable is modified, the Volatile field will reflect the type of
> >variable (Attributes are not reliable; e.g. 0x0 indicates deletion).
> >
> >Cc: Liming Gao <liming.gao@intel.com>
> >Cc: Michael D Kinney <michael.d.kinney@intel.com>
> >Cc: Jian J Wang <jian.j.wang@intel.com>
> >Cc: Hao A Wu <hao.a.wu@intel.com>
> >Signed-off-by: Michael Kubacki <michael.a.kubacki@intel.com>
> >---
> > MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> >diff --git a/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> >b/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> >index 29d6aca993..75d33ff724 100644
> >--- a/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> >+++ b/MdeModulePkg/Universal/Variable/RuntimeDxe/Variable.c
> >@@ -2296,9 +2296,8 @@ UpdateVariable (
> >
> > Done:
> > if (!EFI_ERROR (Status)) {
> >- if (Variable->Volatile) {
> >- VolatileCacheInstance = &(mVariableModuleGlobal-
> >>VariableGlobal.VariableRuntimeCacheContext.VariableRuntimeVolatileCac
> h
> >e);
> >- } else {
> >+ VolatileCacheInstance = &(mVariableModuleGlobal-
> >>VariableGlobal.VariableRuntimeCacheContext.VariableRuntimeVolatileCac
> h
> >e);
> >+ if ((Variable->CurrPtr != NULL && !Variable->Volatile) ||
> >+ (Attributes &
> >EFI_VARIABLE_NON_VOLATILE) != 0) {
> > VolatileCacheInstance = &(mVariableModuleGlobal-
> >>VariableGlobal.VariableRuntimeCacheContext.VariableRuntimeNvCache);
> > }
> >
> >--
> >2.16.2.windows.1
> >
> >
> >
>
next prev parent reply other threads:[~2019-11-11 6:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 5:16 [PATCH V1 1/1] MdeModulePkg/Variable: Fix volatile variable RT cache update logic Kubacki, Michael A
2019-11-11 6:07 ` [edk2-devel] " Liming Gao
2019-11-11 6:11 ` Kubacki, Michael A [this message]
2019-11-12 0:25 ` Liming Gao
2019-11-12 0:55 ` Kubacki, Michael A
2019-11-12 8:53 ` Laszlo Ersek
2019-11-12 5:42 ` Wang, Jian J
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=BY5PR11MB4484BDF21F4DD0E382A8953FB5740@BY5PR11MB4484.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