public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zeng, Star" <star.zeng@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [staging/FmpDevicePkg-master][PATCH] FmpDevicePkg FmpDxe: Initialize DeviceLibLowestSupportedVersion
Date: Mon, 30 Jul 2018 05:41:42 +0000	[thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103BB8A1DA@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8A9CF33@ORSMSX113.amr.corp.intel.com>

Normally, FmpDeviceGetLowestSupportedVersion() should not touch input DeviceLibLowestSupportedVersion when returning an error.
If we think it is legal that DeviceLibLowestSupportedVersion could be updated in an error case by FmpDeviceGetLowestSupportedVersion(), then we could only add new line below before calling FmpDeviceGetLowestSupportedVersion().

DeviceLibLowestSupportedVersion = DEFAULT_LOWESTSUPPORTEDVERSION;


Thanks,
Star

-----Original Message-----
From: Kinney, Michael D 
Sent: Monday, July 30, 2018 1:36 PM
To: Zeng, Star <star.zeng@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: RE: [staging/FmpDevicePkg-master][PATCH] FmpDevicePkg FmpDxe: Initialize DeviceLibLowestSupportedVersion

Star,

I do not think the logic is identical.

The function FmpDeviceGetLowestSupportedVersion() could modify the value of DeviceLibLowestSupportedVersion and return an error.

Mike

> -----Original Message-----
> From: Zeng, Star
> Sent: Sunday, July 29, 2018 7:51 PM
> To: edk2-devel@lists.01.org
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Zeng, Star 
> <star.zeng@intel.com>
> Subject: [staging/FmpDevicePkg-master][PATCH]
> FmpDevicePkg FmpDxe: Initialize
> DeviceLibLowestSupportedVersion
> 
> Update the title to include "[staging/FmpDevicePkg- master]".
> 
> Thanks,
> Star
> -----Original Message-----
> From: Zeng, Star
> Sent: Monday, July 30, 2018 10:50 AM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Kinney, Michael D 
> <michael.d.kinney@intel.com>
> Subject: [PATCH] FmpDevicePkg FmpDxe: Initialize 
> DeviceLibLowestSupportedVersion
> 
> Some static tool reports
> "DeviceLibLowestSupportedVersion" is used, but is uninitialized. It is 
> false positive reporting based because DeviceLibLowestSupportedVersion 
> will have assigned value after
> FmpDeviceGetLowestSupportedVersion() returns SUCCESS.
> 
> This patch refines the code to initialize 
> DeviceLibLowestSupportedVersion to DEFAULT_LOWESTSUPPORTEDVERSION 
> before calling FmpDeviceGetLowestSupportedVersion().
> It can pass the static tool's check.
> 
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Star Zeng <star.zeng@intel.com>
> ---
>  FmpDevicePkg/FmpDxe/FmpDxe.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/FmpDevicePkg/FmpDxe/FmpDxe.c 
> b/FmpDevicePkg/FmpDxe/FmpDxe.c index
> b25a1511c70c..4868f80de2b9 100644
> --- a/FmpDevicePkg/FmpDxe/FmpDxe.c
> +++ b/FmpDevicePkg/FmpDxe/FmpDxe.c
> @@ -229,10 +229,8 @@ GetLowestSupportedVersion (
>    //
>    // Check the FmpDeviceLib
>    //
> -  Status = FmpDeviceGetLowestSupportedVersion
> (&DeviceLibLowestSupportedVersion);
> -  if (EFI_ERROR (Status)) {
> -    DeviceLibLowestSupportedVersion =
> DEFAULT_LOWESTSUPPORTEDVERSION;
> -  }
> +  DeviceLibLowestSupportedVersion =
> DEFAULT_LOWESTSUPPORTEDVERSION;
> + FmpDeviceGetLowestSupportedVersion
> (&DeviceLibLowestSupportedVersion);
> 
>    if (DeviceLibLowestSupportedVersion > ReturnLsv) {
>      ReturnLsv = DeviceLibLowestSupportedVersion;
> --
> 2.7.0.windows.1



  reply	other threads:[~2018-07-30  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30  2:51 [staging/FmpDevicePkg-master][PATCH] FmpDevicePkg FmpDxe: Initialize DeviceLibLowestSupportedVersion Zeng, Star
2018-07-30  5:35 ` Kinney, Michael D
2018-07-30  5:41   ` Zeng, Star [this message]
2018-07-30  5:43     ` Kinney, Michael D

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=0C09AFA07DD0434D9E2A0C6AEB0483103BB8A1DA@shsmsx102.ccr.corp.intel.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