Hello, On Fri, Sep 07, 2007 at 08:38:32PM +0200, Sebastian Siewior wrote: > [...] > > >Christoph encountered a deadlock after a few hours and 16GB of data (on > >an aes-xts-plain partition). Assuming there is an error in xts.c, is > >there an obvious way of finding it? > > Haven't seen any locks in your code, so your part may be fine. How do I > use this? > > cryptsetup -c aes-xts > > or?
for example: cryptsetup --hash sha256 -s 256 -c aes-xts-plain create test /dev/some_partition The 'plain'-iv should give an on-disk format compatible with the requirements of IEEE1619/D16. Internally the 256-bit key is split in two 128-bit AES keys. Other allowed key sizes for aes-xts-* are 2*192=384 bit and 2*256=512 bit. (you may want to use a hash with more bits (I don't know what cryptsetup does if the hash gives less than keysize bits)) Christoph, is your testing machine stable if you run the same test with aes-lrw-plain and the same keysize? Greetings, Rik. -- Nothing is ever a total loss; it can always serve as a bad example. - To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
