| 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
| ||
|
Message-ID: <20140203081506.GA10961@infradead.org> Date: Mon, 3 Feb 2014 00:15:06 -0800 From: Christoph Hellwig <hch@...radead.org> To: Mikulas Patocka <mpatocka@...hat.com> Cc: James Bottomley <James.Bottomley@...senPartnership.com>, Jens Axboe <axboe@...nel.dk>, "Alasdair G. Kergon" <agk@...hat.com>, Mike Snitzer <msnitzer@...hat.com>, dm-devel@...hat.com, "David S. Miller" <davem@...emloft.net>, linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org, Neil Brown <neilb@...e.de>, linux-raid@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH] block devices: validate block device capacity On Fri, Jan 31, 2014 at 03:20:17AM -0500, Mikulas Patocka wrote: > So if you think you can support 16TiB devices and leave pgoff_t 32-bit, > send a patch that does it. > > Until you make it, you should apply the patch that I sent, that prevents > kernel lockups or data corruption when the user uses 16TiB device on > 32-bit kernel. Exactly. I had actually looked into support for > 16TiB devices for a NAS use case a while ago, but when explaining the effort involves the idea was dropped quickly. The Linux block device is too deeply tied to the pagecache to make it easily feasible. -- 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/
Powered by blists - more mailing lists