diff options
author | Zhichao Gao <zhichao.gao@intel.com> | 2020-07-06 14:21:10 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-07-15 01:18:13 +0000 |
commit | a35de0aff3e92c8584419720be199ccfff9b6a43 (patch) | |
tree | d4731eb1dc34cfb86a88299329ee2172654eccb9 /BaseTools/Source/Python/Workspace/WorkspaceDatabase.py | |
parent | 256c4470f86e53661c070f8c64a1052e975f9ef0 (diff) | |
download | edk2-a35de0aff3e92c8584419720be199ccfff9b6a43.tar.gz edk2-a35de0aff3e92c8584419720be199ccfff9b6a43.tar.bz2 edk2-a35de0aff3e92c8584419720be199ccfff9b6a43.zip |
MdeModulePkg/PartitionDxe: Correct the MBR last block value
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2823
PartitionValidMbr function's second parameter should be the
last sector of the device. For MBR partition, the block size is
sector size, i.e. 512 bytes. The original value is media block
last LBA which is counted by the media block size. And media
block size is not always 512 bytes, it may be larger which would
cause the MBR boundary check incorrect. The boundary check is
based on the partition entry start LBA and size of LBA which
are both counted by the sector number (512 bytes).
Cc: Hao A Wu <hao.a.wu@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Workspace/WorkspaceDatabase.py')
0 files changed, 0 insertions, 0 deletions