linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dimitrios Siganos <dimitris@siganos.org>
To: linux-crypto@vger.kernel.org
Subject: Question about async operations
Date: Thu, 04 Mar 2010 17:38:51 +0000	[thread overview]
Message-ID: <4B8FF02B.5090600@siganos.org> (raw)

Hi,

I have a question about the asynchronous characteristics of the crypto api.

1) crypto_alloc_hash("sha1", 0, CRYPTO_ALG_ASYNC), does this code create 
an asynchronous sha1 transform?

2) crypto_alloc_hash("sha1", 0, 0), does this code create a synchronous 
sha1 transform?

3) Is synchronous taken to mean the follwoing? When the function returns 
(and is successful) the result is already computed and placed at the 
destination.

4) Is asynchronous taken to mean the following?  "When the function 
returns (and is successful) we know that a request has been posted for 
the operation to take place but we have no guarantees that the operation 
has completed.

5) If the answer to the above is yes then how can the following style of 
code work? I see such code in many places:
    crypto_alloc_hash("sha1", 0, CRYPTO_ALG_ASYNC);
    crypto_hash_init(&desc);
    rc = crypto_hash_update(&desc, &sg, len);
    rc = crypto_hash_final(&desc, dst);
    now_use_dst(dst);
How can we know that the dst has the right contents when we call 
"now_use_dst(dst)"? Is there something that I am missing?

Regards,
Dimitris

             reply	other threads:[~2010-03-04 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 17:38 Dimitrios Siganos [this message]
2010-03-05  7:33 ` Question about async operations Herbert Xu

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=4B8FF02B.5090600@siganos.org \
    --to=dimitris@siganos.org \
    --cc=linux-crypto@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).