public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Paulo Alcantara <pcacjr@zytor.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Zeng, Star" <star.zeng@intel.com>
Subject: Re: Functionality issues in UDF support
Date: Fri, 15 Sep 2017 12:45:25 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BA42BA2@SHSMSX151.ccr.corp.intel.com> (raw)
In-Reply-To: <c8d7bcb3-9427-dcef-defc-17e8c8a2d0b8@redhat.com>

Laszlo,
I may not state the problem very clearly.
I saw two problems:
1. ParitionDxe shouldn't create BLK handle for the entire media again. Our QA complains
     several new but unexpected BLK devices are seen. This bug is easy to fix and needs to
     be fixed ASAP. So I created a BZ (https://bugzilla.tianocore.org/show_bug.cgi?id=707).

2. PartitionDxe should handle multiple LVDs in a UDF CDROM. No one complains this.
     I am fine to accept the limitation. So I even didn't create a BZ.
     Anyone who wants this support can submit a BZ.
     I guess following the same pattern of existing code to support it should be easy.

Thanks,
Ray

-----Original Message-----
From: Laszlo Ersek [mailto:lersek@redhat.com] 
Sent: Friday, September 15, 2017 7:03 PM
To: Ni, Ruiyu <ruiyu.ni@intel.com>; Paulo Alcantara <pcacjr@zytor.com>; Yao, Jiewen <jiewen.yao@intel.com>
Cc: Wu, Hao A <hao.a.wu@intel.com>; edk2-devel@lists.01.org; Zeng, Star <star.zeng@intel.com>
Subject: Re: [edk2] Functionality issues in UDF support

On 09/15/17 09:38, Ni, Ruiyu wrote:
> Paulo,
> Supporting multiple LVDs can be considered as a long-term task, or can 
> be added per request.
> But I think a urgent fix in PartitionDxe driver is to:
> 1. create child BLK only for the portion covered by the LVD 2. Do not 
> create child BLK for LVD that's actually an Eltorito LVD
> 
> I submitted a Bugzilla to record this:
> https://bugzilla.tianocore.org/show_bug.cgi?id=707

Ray,

from the discussion it looks like the issue only hits with multi-volume media. Paulo stated he had never seen such media. Can you share your reproducer media perhaps (even privately, if it can be done legally), or else provide instructions to create, or obtain, such media?

Thanks!
Laszlo

  reply	other threads:[~2017-09-15 12:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-15  3:33 Functionality issues in UDF support Ni, Ruiyu
2017-09-15  4:57 ` Paulo Alcantara
2017-09-15  5:08   ` Ni, Ruiyu
2017-09-15  5:33     ` Zeng, Star
2017-09-15  5:35       ` Ni, Ruiyu
2017-09-15  5:37     ` Paulo Alcantara
2017-09-15  6:02       ` Ni, Ruiyu
2017-09-15  6:26         ` Paulo Alcantara
2017-09-15  7:01           ` Zeng, Star
2017-09-15  7:08             ` Ni, Ruiyu
2017-09-15  7:10           ` Ni, Ruiyu
2017-09-15  7:22             ` Paulo Alcantara
2017-09-15  7:38               ` Ni, Ruiyu
2017-09-15 10:26                 ` Laszlo Ersek
2017-09-15 11:03                 ` Laszlo Ersek
2017-09-15 12:45                   ` Ni, Ruiyu [this message]
2017-09-15 15:51                 ` Laszlo Ersek
2017-09-15 16:27                   ` Paulo Alcantara
2017-09-15 16:40                     ` Ni, Ruiyu
2017-09-15 16:51                       ` Laszlo Ersek
2017-09-15 23:38                         ` Yao, Jiewen
2017-09-15 23:58                           ` Yao, Jiewen
2017-09-16 21:19                             ` Laszlo Ersek
2017-09-16 20:21                           ` Laszlo Ersek
2017-09-15 16:45                     ` Laszlo Ersek

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=734D49CCEBEEF84792F5B80ED585239D5BA42BA2@SHSMSX151.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