From: Mark Allyn <allyn@well.com>
To: linux-crypto@vger.kernel.org
Subject: Re: Question on __crypto_alg_lookup
Date: Fri, 27 Jan 2012 14:51:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.02.1201271449500.11453@well.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1201271415230.23638@well.com>
Here is a related questions that might help me . . .
Do any of you know of a ahash and ablkcipher driver that is known to have
worked with dm-crypt? I would like to look at that code.
The drivers that I have look at so far seem to set the cra_flags the same
as I have; I want to know if there is a driver that is known to have
worked and look at it's cra_flags settings.
Thank you
Truly,
Mark Allyn
Portland, Oregon
www.allyn.com
971-563-7588
On Fri, 27 Jan 2012, Mark Allyn wrote:
>
> Folks:
>
> In __crypto_alg_lookup, at about line 85 of api.c, there is the following:
>
> if ((q->cra_flags ^ type) & mask)
> continue;
>
> There is no commenting on this at all.
>
> Can someone please explain what this is for and just what is this trying
> to filter?
>
> I am trying to get dm-crypt to work with a ahash device that we have.
>
> The dm-crypt is calling crypto_alloc_hash with "sha256" type 0, and mask 0x
> 80
>
> My driver is setting these flags:
>
> .cra_flags = CRYPTO_ALG_TYPE_AHASH |
> CRYPTO_ALG_ASYNC,
>
> The search seems to be failing at the above sequence in __crypto_alg_lookup.
>
> Is dm-crypt supposed to work with ahash?
>
> The Documentation/crypto does not seem to include much information
> on using the ahash and ablkcipher infrastructure.
>
> There is one document called async-tx-api.txt that seems to have no
> correlation with the ahash or ablkcipher stuff. Is it still valid?
>
> Is there another place I can look for decent documentation?
>
> Thank you
>
> Truly,
>
> Mark Allyn
> Portland, Oregon
> www.allyn.com
> 971-563-7588
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2012-01-27 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 22:23 Question on __crypto_alg_lookup Mark Allyn
2012-01-27 22:51 ` Mark Allyn [this message]
2012-02-01 21:16 ` Herbert Xu
2012-02-02 5:15 ` Mark Allyn
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=alpine.LRH.2.02.1201271449500.11453@well.com \
--to=allyn@well.com \
--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