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? Best Regards, Huang Ying
Attachment:
signature.asc
Description: This is a digitally signed message part
