lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 13 Jan 2009 13:53:41 +1100 From: Herbert Xu <herbert@...dor.apana.org.au> To: Huang Ying <ying.huang@...el.com> Cc: Sebastian Siewior <linux-crypto@...breakpoint.cc>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org> Subject: Re: [RFC PATCH crypto 4/4] AES-NI: Add support to Intel AES-NI instructions for x86_64 platform On Tue, Jan 13, 2009 at 10:49:07AM +0800, Huang Ying wrote: > > I can set req->data in xx_encrypt() to my original request to solve this > issue. Except that, does this solution work? Yes it would work provided that you save the original data somewhere in your context (and then restore it of course). But it'd be much simpler if you just nested the request structures (they aren't that big too start with) which means that you wouldn't need this extra completion handler at all. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists