Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp14275344ybl; Mon, 30 Dec 2019 07:12:36 -0800 (PST) X-Google-Smtp-Source: APXvYqxmcT5EPxODVbaa+kSSEpdB+rOdLORxi4Cbj9fjCJpBpKKqHcvRGwUrTKP/VW2Qk5nqiNGr X-Received: by 2002:aca:bac3:: with SMTP id k186mr5739993oif.19.1577718755850; Mon, 30 Dec 2019 07:12:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577718755; cv=none; d=google.com; s=arc-20160816; b=i+HeygrtL6E7n3FqD5TncFgSE319n8A18c1U/aD5gP9u5rElSs/mLCuWhnjymon7yc uUHs+4kso7DeUBPslGcqYtfq2D/qOpJLZkUGfgJaZzXs+kCPBy+JGdZfFO5gdQGINzJd mJIQX1Qp2x7Y4tkoPdnV3GfBDxRfpRqYIihkP8PJ9tVVumzCLnlgzWJRqsSPg29CLjzK N9jfmVKWUfXpyJsMljWNRO1IAEmjKUQrWQBu//7d08S1+Q4tpkwoPhXqcxgBSip5SQdu gwn6YjqBX1QWeaxlziFarWYnhH648nyNrRvkst8MWZT3NBg8RLKj0xCc7OOxApvwX7Xq PRxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=e3s/WqsE2mHLYt7Hngrm7F8xpgITs0maBNJiKYSk6TA=; b=u7vcRY9h02x8FH4rKCiP2yDF5wztqyuyYgKgeSbPbyWeXneVKUyJdgb+V4QFRJycnK rpAdpvpRulBb0FWvgj28oB2u8R7c0ll9mwRfmyIyOSlmE2vA58DzfJ8fdsw7/3z5Fd88 VKiM4dokuqshkuDMtUrWQ7LnicF/1Q+jH0D2TSAE4TAgAyc4deyT9EZBwXeENzr9ikjS Ui5Rj1l0wwG6H+oCmshpAHwNXT3/Bp0dOR6D2kNNi/jk1Eac3Zx8l9TmSIIh6O0W36eW EigIsV33SXpNlkXreJFt6oGJogd7Iq8kXkNZD/U6/ENyDAhkDoXtN6BsbKYQob+2venl myAg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=gh7FK9xO; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m82si20621774oig.129.2019.12.30.07.12.14; Mon, 30 Dec 2019 07:12:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=gh7FK9xO; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727546AbfL3PLo (ORCPT + 99 others); Mon, 30 Dec 2019 10:11:44 -0500 Received: from mail-wm1-f45.google.com ([209.85.128.45]:40701 "EHLO mail-wm1-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727519AbfL3PLn (ORCPT ); Mon, 30 Dec 2019 10:11:43 -0500 Received: by mail-wm1-f45.google.com with SMTP id t14so14365015wmi.5 for ; Mon, 30 Dec 2019 07:11:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=e3s/WqsE2mHLYt7Hngrm7F8xpgITs0maBNJiKYSk6TA=; b=gh7FK9xO2hmKAPF22jizPP9iHVy7lZ3H1yPZbrPR/URCc4mTqrHAWX9Aovbsx1xvbw Ns03qTiVpiiuMBmij6rQWQUoIhbKEFQaDLJLXZJDwxFB5bL3gmOSZbpVFHwTHoQZ45JB 9xAYeX2CcvRlHBN7q1u9w/Os6YGULVVrJiNUhyi7zFVJV/H/nQje2nL7Y6+GnqPI7RBQ 07DQgUWlhXo5vSRlGvk2S+7VxNEb2hDXPOhbEnrLjI8U9J5misIbV4RlTptUSZV1IJ9U JU6PzICGxiyOXfpGgeVKhM6DBcFSwIGo8WwgzP5T4zXkgUwGqW7yb2GeqlRl8G6/InkS Q5SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=e3s/WqsE2mHLYt7Hngrm7F8xpgITs0maBNJiKYSk6TA=; b=KDuJOXLtLJw10OWTrRPKKaHvjzPJ89gtte+SomFRx6DLlJD6p28RQTDJs7ROSsm7+p qYhm7sgfVjuxBsQlb28jUEqqDbcHLBq0C+L47DeIb2MPDJy8LBg+pw9LrpJMJBEb7fgU sUQrH619itK8+asXtrslR7e8nPKXU/VR3YE9Co33xhsIJnm+zBj1Iy0L7vEbTMLT5Egl DOREDXiULH1xKpqWuGIz3OOsPhyhX2cg3ou82p6p89DLY3wJaxNQ//Wcuy8MXY6L4jGC z0HFesWO0Z8l/XHuE52elQnuNYg0ZapMy0Eoz4IT3/kiNTqJoSNq7GRAdfx2ZSVCjXgL 4O+Q== X-Gm-Message-State: APjAAAU/+3qEz1jSSwYpQsjsqwqnMMn23fxcFzJuqc4dx4GNUypWuCdI yBzrhffBXZaHx4Ui9h0aWm2NHsTEYdvp2uB1gL7a2g== X-Received: by 2002:a1c:9d52:: with SMTP id g79mr35381433wme.148.1577718702089; Mon, 30 Dec 2019 07:11:42 -0800 (PST) MIME-Version: 1.0 References: <6c4fbd8240af542f2c5e26e990825f1232009aaf.camel.ref@cs.com> <6c4fbd8240af542f2c5e26e990825f1232009aaf.camel@cs.com> In-Reply-To: <6c4fbd8240af542f2c5e26e990825f1232009aaf.camel@cs.com> From: Ard Biesheuvel Date: Mon, 30 Dec 2019 16:11:31 +0100 Message-ID: Subject: Re: Internal crypto test fail: changed 'req->iv' To: Richard van Schagen Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Mon, 30 Dec 2019 at 11:10, Richard van Schagen wrote: > > I am writing a module for the EIP93 crypto engine. From what I have > been reading on this mailing list, the driver should return the updated > IV in order for the caller to =E2=80=9Cresume=E2=80=9D or =E2=80=9Ccontin= ue=E2=80=9D with this IV in > another call. > > A code-snippet: > > int ivsize =3D crypto_skcipher_ivsize(skcipher); > > If (ivsize) > memcpy(req->iv, rctx->lastiv, ivsize); > > Where rctx->lastiv was read from the hardware itself. > > The fail message I am getting is: > [ 57.290000] alg: skcipher: changed 'req->iv' > [ 57.370000] alg: skcipher: eip93-cbc-aes encryption co > rrupted request struct on test vector 0, cfg=3D"in-place" > [ 57.380000] alg: skcipher: changed 'req->iv' > [ 57.460000] alg: skcipher: eip93-ctr-aes encryption corrupted > request struct on test vector 0, cfg=3D"in-place" > [ 57.470000] alg: skcipher: changed 'req->iv' > [ 57.560000] alg: skcipher: eip93-rfc3686(ctr)-aes encryption > corrupted request struct on test vector 0, cfg=3D"in-place" > [ 57.570000] alg: skcipher: changed 'req->iv=E2=80=99 > > Where/How should I return the new/updated IV ? > Are you sure you are not making req->iv point to a different buffer?