DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vasile Catalin-B50542 <catalin.vasile@freescale.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] out of order encryption
Date: Thu, 6 Aug 2015 10:00:27 +0300	[thread overview]
Message-ID: <55C3060B.6030206@freescale.com> (raw)

Would dm-crypt execute correctly if sector encryption ended asynchronously?
For example:
If sector 1, 2, 3 are sent to be done asynchronously to the same 
algorithm instance,
and the jobs end in the following order: 2, 1, 3; does the dm-crypt 
module know to
write the data in the proper place when the encryption "done" callback 
is called?

             reply	other threads:[~2015-08-06  8:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  7:00 Vasile Catalin-B50542 [this message]
2015-08-06  9:15 ` [dm-crypt] out of order encryption Milan Broz
2015-08-06 10:12   ` Vasile Catalin-B50542
2015-08-06 10:38   ` Vasile Catalin-B50542
2015-08-06 11:06     ` Milan Broz
2015-08-06 11:19     ` Lars Winterfeld
2015-08-06 11:32       ` Vasile Catalin-B50542
2015-08-06 11:46         ` Lars Winterfeld
2015-08-06 11:48         ` Milan Broz
2015-08-06 12:10           ` Vasile Catalin-B50542
2015-08-06 12:40             ` Milan Broz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C3060B.6030206@freescale.com \
    --to=catalin.vasile@freescale.com \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox