linux-kernel - Re: support for drives larger than 2TiB

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100724232247.GA2129@khazad-dum.debian.net>
Date:	Sat, 24 Jul 2010 20:22:47 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Greg Freemyer <greg.freemyer@...il.com>
Cc:	Yuhong Bao <yuhongbao_386@...mail.com>, tj@...nel.org,
	jeff@...zik.org, ben.collins@...ntu.com, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: support for drives larger than 2TiB

On Sat, 24 Jul 2010, Greg Freemyer wrote:
> Secondly, if you look at the table on the right of
> http://en.wikipedia.org/wiki/Master_boot_record#Disk_partitioning you
> see that the starting sector of a partition is defined with a 32-bit
> value.
> 
> ie. 2TB with 512 byte sectors.
> 
> The normal solution is to move to a GPT which requires EFI if you want
> to boot from it.

Can't one have a GPT with a guard boot sector which can read the real
partition table?

I think Tejun must mean some big problem at the BIOS APIs required for the
bootloader.  Tejun, what exactly croaks at the 2TB boundary (with 512KiB
sectors)?

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/