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
| ||
|
Date: Fri, 4 Jun 2010 13:09:43 +1000 From: Nick Piggin <npiggin@...e.de> To: "Martin K. Petersen" <martin.petersen@...cle.com> Cc: Chris Mason <chris.mason@...cle.com>, James Bottomley <James.Bottomley@...e.de>, Matthew Wilcox <matthew@....cx>, Christof Schmitt <christof.schmitt@...ibm.com>, Boaz Harrosh <bharrosh@...asas.com>, linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: Wrong DIF guard tag on ext2 write On Thu, Jun 03, 2010 at 09:46:02PM -0400, Martin K. Petersen wrote: > >>>>> "Nick" == Nick Piggin <npiggin@...e.de> writes: > > Nick> Also I don't think we can deal with memory errors and scribbles > Nick> just by crcing dirty data. The calculations generating the data > Nick> could get corrupted. > > Yep, the goal is to make the window as small as possible. > > > Nick> Data can be corrupted on its way back from the device to > Nick> userspace. > > We also get a CRC back from the storage. So the (integrity-aware) > application is also able to check on read. Well that's nice :) > Nick> Obviously this feature is being pushed by databases and such that > Nick> really want to pass checksums all the way from userspace. Block > Nick> retrying is _not_ needed or wanted here of course. > > Nope. The integrity error is bubbled all the way up to the database and > we can decide to retry, recreate or error out depending on what we find > when we do validation checks on the data buffer and the integrity > metadata. By block retrying, I just meant the bounce / re-checksum approach. -- 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