grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Skip Apple ghosts
Date: Tue, 24 Dec 2013 18:00:23 +0100	[thread overview]
Message-ID: <52B9BDA7.4030306@gmail.com> (raw)
In-Reply-To: <1387903453.918.53.camel@opensuse.site>

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

On 24.12.2013 17:44, Andrey Borzenkov wrote:
> В Вт, 24/12/2013 в 14:26 +0100, Vladimir 'φ-coder/phcoder' Serbinenko
> пишет:
>> Hello, all. It was discovered that on macs sometimes firmware defines
>> ghost disks with vendor suffix. E.g.
>> /ACPI(a0341d0,0)/PCI(2,1f)/UnknownMessaging(12)/EndEntire
>> is a normal disks with partitions presented with HD(...) but then
>> /ACPI(a0341d0,0)/PCI(2,1f)/UnknownMessaging(12)/MediaVendor(Apple)[0:
>> ]/EndEntire
>> is a ghost disk. It has as suffix a vendor path with empty vendor data.
> 
> Messaging subtype 12 is IPv4 Device Path. I suppose it is related to
> NetBoot.
It's hex. 0x12 is SATA.
> 
>> This is a problem because when chainloading on such disks GRUB can't
>> find handle of partition as none is defined. I propose to dkip ghosts
>> completely. This should be safe as the skip happens only for empty Apple
>> vendor suffix and if the parent is already a known disk.
> 
> Hmm ... should not we simply ignore all unknown media types? They can be
> added on case by case basis I guess.
> 
Too much breakage potential. And I don't have accessto check it on loads
of different buggy EFI systems and even if I did, it would be a waste of
time.
> diff --git a/grub-core/disk/efi/efidisk.c b/grub-core/disk/efi/efidisk.c
> index e04203f..6dfdb0d 100644
> --- a/grub-core/disk/efi/efidisk.c
> +++ b/grub-core/disk/efi/efidisk.c
> @@ -310,6 +310,7 @@ name_devices (struct grub_efidisk_data *devices)
>               grub_efi_print_device_path (d->device_path);
>  #endif
>               /* For now, ignore the others.  */
> +             d->last_device_path = 0;
>               break;
>             }
>         }
> 
> 
>> Did anyone see anything similar?
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
> 
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]

  reply	other threads:[~2013-12-24 17:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24 13:26 [PATCH] Skip Apple ghosts Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-24 16:44 ` Andrey Borzenkov
2013-12-24 17:00   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2014-01-07 18:17 ` Andrey Borzenkov
2014-01-07 18:20 ` Andrey Borzenkov

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-all 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=52B9BDA7.4030306@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).