linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian-Ken Rueegsegger <ken@codelabs.ch>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, steffen.klassert@secunet.com
Subject: Re: [PATCH 0/4] Switch remaining algorithms to shash
Date: Thu, 04 Dec 2008 08:55:57 +0100	[thread overview]
Message-ID: <49378D0D.8090201@codelabs.ch> (raw)
In-Reply-To: <20081204064812.GB18141@gondor.apana.org.au>

Hello Herbert,

Herbert Xu wrote:
> On Thu, Dec 04, 2008 at 01:18:08AM +0100, Adrian-Ken Rueegsegger wrote:
>> The first patch removes the message schedule W from struct sha512_ctx
>> since it gets calculated anew on each execution of sha512_transform. This
>> reduces the size of sha512_ctx considerably and will allow it to be
>> registered as a shash algorithm (it will pass the size check in
>> crypto_register_shash (crypto/shash.c:490)).
>> Herbert, could you explain why descsize must be smaller (or equal)
>> than PAGE_SIZE / 8?
> 
> This is so that people can put it on the stack safely.  So moving
> things out of the context and onto the stack because it's too big
> is a no-no :)

Thanks for the explanation.

> Perhaps store in a static percpu area?
> 
>> The next two patches switch sha512 and wp512 to the new shash interface.
> 
> BTW, in order to add missing Kconfig dependencies on HASH I've
> just rebased my tree and updated all the shash conversion patches.
> So please resend them with the Kconfig bits added.

Will do. I will resubmit the patches later today.

>> The fourth patch is another try to convert michael_mic. The key values
>> l and r are duplicated in the descriptor part since they are used and
>> changed during the actual transformation. I would be gratefull for
>> comments on this patch since I am not sure it's the proper way to do it.
> 
> Since they're read-only they should be obtained from the tfm context
> when needed, just like crc32c.

If I read the code correctly l and r are not read-only, e.g. in
michael_update there are multiple assignments to mctx->l and mctx->r.
That's the reason why I left them in the desc context.

Thank you for your comments,
Adrian

  reply	other threads:[~2008-12-04  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04  0:18 [PATCH 0/4] Switch remaining algorithms to shash Adrian-Ken Rueegsegger
2008-12-04  0:18 ` [PATCH 1/4] crypto: sha512 - Remove W (message schedule) from struct sha512_ctx Adrian-Ken Rueegsegger
2008-12-04  0:18   ` [PATCH 2/4] crypto: sha512 - Switch to shash Adrian-Ken Rueegsegger
2008-12-04  0:18     ` [PATCH 3/4] crypto: wp512 " Adrian-Ken Rueegsegger
2008-12-04  0:18       ` [PATCH 4/4][RFC] crypto: michael_mic " Adrian-Ken Rueegsegger
2008-12-04  3:29         ` Herbert Xu
2008-12-04  8:04           ` Adrian-Ken Rueegsegger
2008-12-04  6:48 ` [PATCH 0/4] Switch remaining algorithms " Herbert Xu
2008-12-04  7:55   ` Adrian-Ken Rueegsegger [this message]
2008-12-04  8:02     ` 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=49378D0D.8090201@codelabs.ch \
    --to=ken@codelabs.ch \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    /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).