public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Edwards, Craig" <Craig.Edwards@dell.com>
To: "gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
	"jian.j.wang@intel.com" <jian.j.wang@intel.com>,
	"hao.a.wu@intel.com" <hao.a.wu@intel.com>,
	"ray.ni@intel.com" <ray.ni@intel.com>,
	"zhichao.gao@intel.com" <zhichao.gao@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Shutt, Mark" <Mark.Shutt@dell.com>
Subject: [Patch MBR endless loop hang with invalid LBA0 1/1] MdeModulePkg/PartitionDxe: Add break to handle invalid LBA0 in MBR
Date: Wed, 5 Jan 2022 18:53:12 +0000	[thread overview]
Message-ID: <SA1PR19MB516828F7611B1403EC2D8B77E74B9@SA1PR19MB5168.namprd19.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2175 bytes --]

 Read Disk does a modification of ExtMbrStartingLba with the code MultU64x32
 (ExtMbrStartingLba, BlockSize) Error detection to see if ExtMbrStartingLBA
 has a value of 0. This is invalid as LBA 0 = MBR. After modification, the
 next time ExtMbrStartingLba is in this function if ExtMbrStartingLba is set
 to 0 in the MBR it never passes the while/do evaluation It is multiplied by 0
 by read disk , set to 0 by an invalid MBR and goes back to evaluation This
 condition will also cause Ws19 and WS22 to hang, however Microsoft has
 developed a hotfix patch that will be released in 2022

Cc: Liming Gao <gaoliming@byosoft.com.cn<mailto:gaoliming@byosoft.com.cn>>
Cc: Jian J Wang <jian.j.wang@intel.com<mailto:jian.j.wang@intel.com>>
Cc: Hao A Wu <hao.a.wu@intel.com<mailto:hao.a.wu@intel.com>>
Cc: Ray Ni <ray.ni@intel.com<mailto:ray.ni@intel.com>>
Cc: Zhichao Gao <zhichao.gao@intel.com<mailto:zhichao.gao@intel.com>>

Signed-off-by: Craig Edwards <craig.edwards@dell.com<mailto:craig.edwards@dell.com>>

 Date:      Wed Jan 5 12:27:46 2022 -0600

 On branch graceful_handle_mbr_hang_edit1
 Changes to be committed:
        modified:   MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c
---
 MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c b/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c
index 0f8dc5486521..ad18840e5efd 100644
--- a/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c
+++ b/MdeModulePkg/Universal/Disk/PartitionDxe/Mbr.c
@@ -293,6 +293,12 @@ PartitionInstallMbrChildHandles (
           (Mbr->Partition[0].OSIndicator == EXTENDED_WINDOWS_PARTITION))
       {
         ExtMbrStartingLba = UNPACK_UINT32 (Mbr->Partition[0].StartingLBA);
+          //
+          // A value of 0 is invalid for StartingLBA
+          //
+          if (ExtMbrStartingLba == 0) {
+            break;
+          }
         continue;
       }

--
2.32.0.windows.1





Craig Edwards
Software Engineer
Dell | GDP | PSE | COMMS | BIOS
Craig_Edwards@Dell.com<mailto:Craig_Edwards@Dell.com%0d>




Internal Use - Confidential


[-- Attachment #2: Type: text/html, Size: 6733 bytes --]

             reply	other threads:[~2022-01-05 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05 18:53 Edwards, Craig [this message]
2022-01-06  3:20 ` [Patch MBR endless loop hang with invalid LBA0 1/1] MdeModulePkg/PartitionDxe: Add break to handle invalid LBA0 in MBR Wu, Hao A
2022-01-10  7:18   ` [edk2-devel] " Wu, Hao A

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=SA1PR19MB516828F7611B1403EC2D8B77E74B9@SA1PR19MB5168.namprd19.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