On 06/02/2008 Greg KH wrote: > 2.6.23-stable review patch. If anyone has any objections, please let us know. > ------------------ > From: Milan Broz <mbroz@xxxxxxxxxx> > > patch 91e106259214b40e992a58fb9417da46868e19b2 in mainline. > > Fix possible max_phys_segments violation in cloned dm-crypt bio. > > In write operation dm-crypt needs to allocate new bio request > and run crypto operation on this clone. Cloned request has always > the same size, but number of physical segments can be increased > and violate max_phys_segments restriction. > > This can lead to data corruption and serious hardware malfunction. > This was observed when using XFS over dm-crypt and at least > two HBA controller drivers (arcmsr, cciss) recently. > > Fix it by using bio_add_page() call (which tests for other > restrictions too) instead of constructing own biovec. Does that mean, that at least one prominent reason for data corruption with dm-crypt is fixed in linux kernel 2.6.23+? thanks for the great work, jonas --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
