diff options
author | Davidlohr Bueso <davidlohr@hp.com> | 2013-09-11 14:24:58 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-09-11 15:59:16 -0700 |
commit | b05ebbbbeb67a420d06567c6b9618a9e644d6104 (patch) | |
tree | c8191dab1a7a18752afbb4158e1ad988fbfc0779 /Documentation/blockdev | |
parent | 3e69ac344007bec5e3987ac86619e140fbc79b72 (diff) | |
download | linux-exynos-b05ebbbbeb67a420d06567c6b9618a9e644d6104.tar.gz linux-exynos-b05ebbbbeb67a420d06567c6b9618a9e644d6104.tar.bz2 linux-exynos-b05ebbbbeb67a420d06567c6b9618a9e644d6104.zip |
partitions/efi: detect hybrid MBRs
One of the biggest problems with GPT is compatibility with older, non-GPT
systems. The problem is addressed by creating hybrid mbrs, an extension,
or variant, of the traditional protective mbr. This contains, apart from
the 0xEE partition, up three additional primary partitions that point to
the same space marked by up to three GPT partitions. The result is that
legacy OSs can see the three required MBR partitions and at the same time
ignore the GPT-aware partitions that protect the GPT structures.
While hybrid MBRs are hacks, workarounds and simply not part of the GPT
standard, they do exist and we have no way around them. For instance, by
default, OSX creates a hybrid scheme when using multi-OS booting.
In order for Linux to properly discover protective MBRs, it must be made
aware of devices that have hybrid MBRs. No functionality is changed by
this patch, just a debug message informing the user of the MBR scheme that
is being used.
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Davidlohr Bueso <davidlohr@hp.com>
Reviewed-by: Karel Zak <kzak@redhat.com>
Acked-by: Matt Fleming <matt.fleming@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/blockdev')
0 files changed, 0 insertions, 0 deletions