Messages in this thread | ![/](/images/icornerl.gif) | | Date | Sat, 16 Aug 2003 23:28:47 -0500 | From | Matt Mackall <> | Subject | Re: [RFC][PATCH] Make cryptoapi non-optional? |
| |
On Sat, Aug 16, 2003 at 01:40:56PM -0700, Adam J. Richter wrote: > At 2003-08-16 15:51:10, Matt Mackall wrote: > >The > >current code uses the stack (though currently rather a lot of it), > >which lets it be fully re-entrant. Not an option with cryptoapi. > > I posted a patch a while ago on one of the linux crypto > mailing lists that defined these routines to support allocating > crypto_tfm's on the stack: > > int crypto_tfm_alloc_size(struct crypto_alg *alg, u32 tfm_flags); > int crypto_tfm_init(struct crypto_tfm *tfm, struct crypto_alg *alg, > u32 tfm_flags); > > The patch also created crypto_alg_{get,put} routines so that > crypto_tfm's could be created quickly without having to look up and > release references to crypto_alg's.
Indeed. I suggested pretty much the same thing earlier in this thread and got shot down by davem.
-- Matt Mackall : http://www.selenic.com : of or relating to the moon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |