public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Xu, Min M" <min.m.xu@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	James Bottomley <jejb@linux.ibm.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	"Lee, Chun-Yi" <jlee@suse.com>
Subject: Re: [PATCH v2] OvmfPkg/PlatformInitLib: Fix integrity checking failed of NvVarStore in some cases
Date: Sat, 17 Dec 2022 03:17:42 +0000	[thread overview]
Message-ID: <MW4PR11MB5872B43102C7225A36CF064B8CE79@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221215142723.9788-1-jlee@suse.com>

Thanks for the fix.
Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>

Question: Have you run tiano CI by yourself, before submit the patch?



> -----Original Message-----
> From: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> Sent: Thursday, December 15, 2022 10:27 PM
> To: devel@edk2.groups.io
> Cc: Xu, Min M <min.m.xu@intel.com>; Gerd Hoffmann
> <kraxel@redhat.com>; Yao, Jiewen <jiewen.yao@intel.com>; Tom Lendacky
> <thomas.lendacky@amd.com>; James Bottomley <jejb@linux.ibm.com>;
> Aktas, Erdem <erdemaktas@google.com>; Lee, Chun-Yi <jlee@suse.com>
> Subject: [PATCH v2] OvmfPkg/PlatformInitLib: Fix integrity checking failed of
> NvVarStore in some cases
> 
> In the commit 4f173db8b4 "OvmfPkg/PlatformInitLib: Add functions for
> EmuVariableNvStore", it introduced a PlatformValidateNvVarStore() function
> for checking the integrity of NvVarStore.
> 
> In some cases when the VariableHeader->StartId is VARIABLE_DATA, the
> VariableHeader->State is not just one of the four primary states:
> VAR_IN_DELETED_TRANSITION, VAR_DELETED, VAR_HEADER_VALID_ONLY,
> VAR_ADDED.
> The state may combined two or three states, e.g.
> 
>     0x3C = (VAR_IN_DELETED_TRANSITION & VAR_ADDED) & VAR_DELETED
> or
>     0x3D = VAR_ADDED & VAR_DELETED
> 
> When the variable store has those variables, system booting/rebooting will
> hangs in a ASSERT:
> 
> NvVarStore Variable header State was invalid.
> ASSERT
> /mnt/working/source_code-
> git/edk2/OvmfPkg/Library/PlatformInitLib/Platform.c(819):
> ((BOOLEAN)(0==1))
> 
> Adding more log to UpdateVariable() and PlatformValidateNvVarStore(), we
> saw some variables which have 0x3C or 0x3D state in store.
> e.g.
> 
> UpdateVariable(), VariableName=BootOrder
> L1871, State=0000003F			<-- VAR_ADDED
> State &= VAR_DELETED=0000003D
> FlushHobVariableToFlash(), VariableName=BootOrder
> ...
> UpdateVariable(), VariableName=InitialAttemptOrder
> L1977, State=0000003F
> State &= VAR_IN_DELETED_TRANSITION=0000003E
> L2376, State=0000003E
> State &= VAR_DELETED=0000003C
> FlushHobVariableToFlash(), VariableName=InitialAttemptOrder
> ...
> UpdateVariable(), VariableName=ConIn
> L1977, State=0000003F
> State &= VAR_IN_DELETED_TRANSITION=0000003E
> L2376, State=0000003E
> State &= VAR_DELETED=0000003C
> FlushHobVariableToFlash(), VariableName=ConIn
> ...
> 
> So, only allowing the four primary states is not enough. This patch changes
> the falid states list (Follow Jiewen Yao's suggestion):
> 
> 1. VAR_HEADER_VALID_ONLY (0x7F)
> 	- Header added (*)
> 2. VAR_ADDED (0x3F)
> 	- Header + data added
> 3. VAR_ADDED & VAR_IN_DELETED_TRANSITION (0x3E)
> 	- marked as deleted, but still valid, before new data is added. (*)
> 4. VAR_ADDED & VAR_IN_DELETED_TRANSITION & VAR_DELETED (0x3C)
> 	- deleted, after new data is added.
> 5. VAR_ADDED & VAR_DELETED (0x3D)
> 	- deleted directly, without new data.
> (*) means to support surprise shutdown.
> 
> And removed (VAR_IN_DELETED_TRANSITION) and (VAR_DELETED) because
> they are
> invalid states.
> 
> v2:
> Follow Jiewen Yao's suggestion to add the following valid states:
> 	VAR_ADDED & VAR_DELETED (0x3D)
> 	VAR_ADDED & VAR_IN_DELETED_TRANSITION (0x3E)
> 	VAR_ADDED & VAR_IN_DELETED_TRANSITION & VAR_DELETED
> (0x3C)
> and removed the following invalid states:
> 	VAR_IN_DELETED_TRANSITION
> 	VAR_DELETED
> 
> Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
> ---
>  OvmfPkg/Library/PlatformInitLib/Platform.c | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/OvmfPkg/Library/PlatformInitLib/Platform.c
> b/OvmfPkg/Library/PlatformInitLib/Platform.c
> index 77f22de046..6963c47e0b 100644
> --- a/OvmfPkg/Library/PlatformInitLib/Platform.c
> +++ b/OvmfPkg/Library/PlatformInitLib/Platform.c
> @@ -702,10 +702,11 @@ PlatformValidateNvVarStore (
> 
>        VariableOffset = NvVarStoreHeader->Size - sizeof
> (VARIABLE_STORE_HEADER);
>      } else {
> -      if (!((VariableHeader->State == VAR_IN_DELETED_TRANSITION) ||
> -            (VariableHeader->State == VAR_DELETED) ||
> -            (VariableHeader->State == VAR_HEADER_VALID_ONLY) ||
> -            (VariableHeader->State == VAR_ADDED)))
> +      if (!((VariableHeader->State == VAR_HEADER_VALID_ONLY) ||
> +	    (VariableHeader->State == VAR_ADDED) ||
> +	    (VariableHeader->State == (VAR_ADDED & VAR_DELETED)) ||
> +	    (VariableHeader->State == (VAR_ADDED &
> VAR_IN_DELETED_TRANSITION)) ||
> +	    (VariableHeader->State == (VAR_ADDED &
> VAR_IN_DELETED_TRANSITION & VAR_DELETED))))
>        {
>          DEBUG ((DEBUG_ERROR, "NvVarStore Variable header State was
> invalid.\n"));
>          return FALSE;
> --
> 2.35.3


  reply	other threads:[~2022-12-17  3:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 14:27 [PATCH v2] OvmfPkg/PlatformInitLib: Fix integrity checking failed of NvVarStore in some cases Lee, Chun-Yi
2022-12-17  3:17 ` Yao, Jiewen [this message]
2022-12-20  7:09   ` [edk2-devel] " joeyli
2022-12-21  8:46     ` Yao, Jiewen
2022-12-23  5:54       ` joeyli
     [not found] ` <1731765A81E3FBB0.6436@groups.io>
2022-12-20  5:34   ` Yao, Jiewen

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=MW4PR11MB5872B43102C7225A36CF064B8CE79@MW4PR11MB5872.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