As far as I understand, your commands are used to set up the crypto mapper. They should be executed previous to any read/write operations. I think Milan was talking about read/write operations that are executed after the crypto mapper has been set up successfully. Btw... I guess that if two write operations result in two different changes in the same sector, there are no write conflicts, because for each write, the current sector contents is decrypted first, changes are applies, encrypted and written back. Is that correct? Am 06.08.2015 um 13:32 schrieb Vasile Catalin-B50542: > I am sending crypto requests to a hardware component which has > an option to keeping them in order or not. I was trying to use the out of > order option because this would let requests run in parallel. > If I tried running them with the out of order option bun then I get: > No key available with this passphrase. > When trying to execute the following commands: > cryptsetup -c aes-xts-plain -y -v luksFormat /dev/sda1 > cryptsetup open /dev/sda1 test_xts1 > > On 06.08.2015 14:19, Lars Winterfeld wrote: >> Am 06.08.2015 um 12:38 schrieb Vasile Catalin-B50542: >>> Does the underlying encryption layer (CryptoAPI) have to ensure the >>> complete callbacks are called in the order the requests were submitted? >> Are you thinking about parallelization or asynchronous processing? >>
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
