linux-kernel - Re: 4K disk block and disks larger than 2TiB bugs

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] [day] [month] [year] [list]

Message-ID: <20100217092545.GA16508@infradead.org>
Date:	Wed, 17 Feb 2010 04:25:45 -0500
From:	Christoph Hellwig <hch@...radead.org>
To:	Daniel Taylor <Daniel.Taylor@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 4K disk block and disks larger than 2TiB bugs

On Tue, Feb 16, 2010 at 08:14:27PM -0800, Daniel Taylor wrote:
> The larger problem is for EFI.  There is a significant amount of hard-coded
> assumption that LBAs are 512 bytes.  It would help if I could work with the
> designer to make (and test) the changes in a way that abstracts away the
> size (I do know that the kernel always thinks of disks in units of 512-byte
> blocks).  I have seen attempts in the past to fix this problem, but the
> patches
> were rejected with erroneous comments about fixing it in user space.  If the
> kernel will not recognise the partitions, or assigns incorrect values to the
> starting block and/or number of blocks, there is nothing that user space can
> do with the disk, except notice the EINVAL responses.

This should be fixed since commit 7d13af3279985f554784a45cc961f706dbcdbdd1,
which is included in Linux 2.6.32.

--
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/