From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, ray.ni@intel.com, "Gao,
Zhichao" <zhichao.gao@intel.com>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdeModulePkg/PartitionDxe: Seperate the Udf handler
Date: Wed, 24 Jun 2020 13:57:36 +0200 [thread overview]
Message-ID: <2f85dc90-41ae-0b51-4512-d65dbdd143b5@redhat.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5C5D1BBB@SHSMSX104.ccr.corp.intel.com>
On 06/24/20 10:32, Ni, Ray wrote:
> Zhichao,
> Will two BlockIo child devices cover the same range in the ISO after your patch?
>
> I don't think that's a valid behavior.
Right; I'm surprised to find the Red Hat reference in both the commit
message and the BZ.
I can't say I understand the issue at hand, but are we sure this isn't a
bug -- a standards conformance problem -- with the ISO in question?
Zhichao, do you have a link to an ISO image that triggers the problem,
and can you provide a hexdump of the part of the image that is either
buggy, or triggers the problem in edk2? With a more specific issue
description, I might be able to find someone at Red Hat who could
comment with more insight than myself.
Thanks!
Laszlo
>
> Thanks,
> Ray
>
>> -----Original Message-----
>> From: Gao, Zhichao <zhichao.gao@intel.com>
>> Sent: Wednesday, June 24, 2020 1:56 PM
>> To: devel@edk2.groups.io
>> Cc: Wu, Hao A <hao.a.wu@intel.com>; Ni, Ray <ray.ni@intel.com>; Wang, Jian J <jian.j.wang@intel.com>; Gao, Liming
>> <liming.gao@intel.com>
>> Subject: [PATCH] MdeModulePkg/PartitionDxe: Seperate the Udf handler
>>
>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2823
>>
>> Some linux iso like Redhat would contain both MBR info in the first
>> 512 bytes and volume info at the beginning of 32KB offset.
>> But the partition driver would only choose one of the GPT, MBR, and
>> UDF(el torito compatible) to install the partition. That would lose
>> one info for such linux ISO during one connect. And UDF(el torito
>> compatible) is not conflicted with MBR/GPT. So partition driver should
>> check UDF and MBR/GPT separately.
>>
>> Cc: Hao A Wu <hao.a.wu@intel.com>
>> Cc: Ray Ni <ray.ni@intel.com>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>> Cc: Liming Gao <liming.gao@intel.com>
>> Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
>> ---
>> .../Universal/Disk/PartitionDxe/Partition.c | 52 +++++++++++++------
>> 1 file changed, 37 insertions(+), 15 deletions(-)
>>
>> diff --git a/MdeModulePkg/Universal/Disk/PartitionDxe/Partition.c
>> b/MdeModulePkg/Universal/Disk/PartitionDxe/Partition.c
>> index d1c878ad2e..562490db4f 100644
>> --- a/MdeModulePkg/Universal/Disk/PartitionDxe/Partition.c
>> +++ b/MdeModulePkg/Universal/Disk/PartitionDxe/Partition.c
>> @@ -5,7 +5,7 @@
>> MBR, and GPT partition schemes are supported.
>>
>> Copyright (c) 2018 Qualcomm Datacenter Technologies, Inc.
>> -Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
>> +Copyright (c) 2006 - 2020, Intel Corporation. All rights reserved.<BR>
>> SPDX-License-Identifier: BSD-2-Clause-Patent
>>
>> **/
>> @@ -39,7 +39,6 @@ EFI_DRIVER_BINDING_PROTOCOL gPartitionDriverBinding = {
>> PARTITION_DETECT_ROUTINE mPartitionDetectRoutineTable[] = {
>> PartitionInstallGptChildHandles,
>> PartitionInstallMbrChildHandles,
>> - PartitionInstallUdfChildHandles,
>> NULL
>> };
>>
>> @@ -189,6 +188,8 @@ PartitionDriverBindingStart (
>> {
>> EFI_STATUS Status;
>> EFI_STATUS OpenStatus;
>> + EFI_STATUS UdfStatus;
>> + EFI_STATUS GptMbrStatus;
>> EFI_BLOCK_IO_PROTOCOL *BlockIo;
>> EFI_BLOCK_IO2_PROTOCOL *BlockIo2;
>> EFI_DISK_IO_PROTOCOL *DiskIo;
>> @@ -300,26 +301,47 @@ PartitionDriverBindingStart (
>> if (BlockIo->Media->MediaPresent ||
>> (BlockIo->Media->RemovableMedia && !BlockIo->Media->LogicalPartition)) {
>> //
>> - // Try for GPT, then legacy MBR partition types, and then UDF and El Torito.
>> - // If the media supports a given partition type install child handles to
>> - // represent the partitions described by the media.
>> + // Try for UDF (El TOrito compatible) and GPT/MBR partition types.
>> + // If the media supports a given partition type, it would install child handles
>> + // to represent the partitions described by the media.
>> + // Notes: GPT is conflicted with MBR. It would only install one of them to describe
>> + // the partition. UDF (or El Torito) can exist with MBR, so need to check it along with
>> + // GPT/MBR.
>> //
>> + UdfStatus = PartitionInstallUdfChildHandles (
>> + This,
>> + ControllerHandle,
>> + DiskIo,
>> + DiskIo2,
>> + BlockIo,
>> + BlockIo2,
>> + ParentDevicePath
>> + );
>> +
>> Routine = &mPartitionDetectRoutineTable[0];
>> while (*Routine != NULL) {
>> - Status = (*Routine) (
>> - This,
>> - ControllerHandle,
>> - DiskIo,
>> - DiskIo2,
>> - BlockIo,
>> - BlockIo2,
>> - ParentDevicePath
>> - );
>> - if (!EFI_ERROR (Status) || Status == EFI_MEDIA_CHANGED || Status == EFI_NO_MEDIA) {
>> + GptMbrStatus = (*Routine) (
>> + This,
>> + ControllerHandle,
>> + DiskIo,
>> + DiskIo2,
>> + BlockIo,
>> + BlockIo2,
>> + ParentDevicePath
>> + );
>> + if (!EFI_ERROR (GptMbrStatus) || GptMbrStatus == EFI_MEDIA_CHANGED || GptMbrStatus == EFI_NO_MEDIA) {
>> break;
>> }
>> Routine++;
>> }
>> +
>> + if (!EFI_ERROR (UdfStatus) || !EFI_ERROR (GptMbrStatus)) {
>> + Status = EFI_SUCCESS;
>> + } else if (UdfStatus == EFI_MEDIA_CHANGED || GptMbrStatus == EFI_MEDIA_CHANGED) {
>> + Status = EFI_MEDIA_CHANGED;
>> + } else if (UdfStatus == EFI_NO_MEDIA || GptMbrStatus == EFI_NO_MEDIA) {
>> + Status = EFI_NO_MEDIA;
>> + }
>> }
>> //
>> // In the case that the driver is already started (OpenStatus == EFI_ALREADY_STARTED),
>> --
>> 2.21.0.windows.1
>
>
>
>
next prev parent reply other threads:[~2020-06-24 11:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 5:56 [PATCH] MdeModulePkg/PartitionDxe: Seperate the Udf handler Gao, Zhichao
2020-06-24 8:32 ` Ni, Ray
2020-06-24 11:57 ` Laszlo Ersek [this message]
2020-06-25 0:21 ` [edk2-devel] " Ni, Ray
2020-06-25 9:02 ` Laszlo Ersek
2020-06-29 1:47 ` Gao, Zhichao
2020-06-29 2:42 ` Ni, Ray
2020-06-29 5:23 ` Gao, Zhichao
2020-07-02 9:42 ` Laszlo Ersek
2020-07-06 2:55 ` Gao, Zhichao
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=2f85dc90-41ae-0b51-4512-d65dbdd143b5@redhat.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