On Fri, Feb 27, 2009 at 01:31:56PM +0800, Huang Ying wrote: > Hi, Herbert, > > I had ever heard from you that the only thing guaranteed in the > completion function of async ablkcipher cryption is the req->data has > the value you set before. The request pointer itself may be changed. But > in dm-crypt, I found they rely on request pointer in completion > function: kcryptd_async_done. This makes my AES-NI cryptd usage panic. > > Do you think that is a bug? Absolutely. It should use cc->req instead. Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> 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-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
