| 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: <498521B8.1020703@kernel.org> Date: Sun, 01 Feb 2009 13:14:48 +0900 From: Tejun Heo <tj@...nel.org> To: Jeff Garzik <jeff@...zik.org> CC: linux-ide@...r.kernel.org, jens.axboe@...cle.com, linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org, James.Bottomley@...senPartnership.com, Mauelshagen@...Hat.com, dm-devel@...Hat.com Subject: Re: [PATCHSET] block,scsi,libata: implement alt_size Hello, Jeff. Jeff Garzik wrote: > But the net result is that you are telling dmraid that it is OK to > proceed, even though part of the disk it wants is really missing. That > seems unwise, because are you not basically proceeding with a known > corrupt dataset at that point? Can you elaborate a bit? I don't really understand what you mean. To clarify... * What happens now. BIOS sets up HPA expecting the raid driver to look at the metadata which is at fixed offset from the end of the HPA locked size. dmraid doesn't know about it so looks at the wrong place. Results can be failed assembly or corrupt assembly depending on what's actually on the disk. * With the patches applied. BIOS does the same but libata tells dmraid the BIOS size. dmraid looks at the same offset as the BIOS and everything is well. Thanks. -- tejun -- 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