Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp3199652ybg; Mon, 28 Oct 2019 09:01:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqxlMNIgGJXjnLM0pc2WsnBrqDcrAZUzN0L7OH3UTPRj9vsg/U/cxk0gmP89wh8sCx5V7DIm X-Received: by 2002:aa7:d281:: with SMTP id w1mr19959243edq.154.1572278474466; Mon, 28 Oct 2019 09:01:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572278474; cv=none; d=google.com; s=arc-20160816; b=vJESA7zj3hccExbDjIRDr42uC91z+mgV7tXab30q/8GxdyfhESRIuLD7yZ6Sp7wEBj IzNpXo+mur+dZKWDP5Kuu/djhIxA7JX16LcVRCaTrqE8qEbbR7qIgddd7kTpBS6hGHhd JETz6C8D9isoqNzDW2m+rTWq/o2h3kk0MnQV6ZsY0k9MOLtqMMEn9ODTfFqsRGxGP3iv /rD3XevsWPiyAQpXaHAglN0ChjzBEvT4XpL1VoU/TAYvkpAQ8KX4nK+U12koe6HPGNEX p98HNeeJcQz0m8Kckk1P8ejeCHqJB2cqkJZeJnZwG0xQNKTrVYS0U8ebKrSg9H0euOEK 3TCA== 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=llIvbuQZkok97wxZ5YRzO3v5zhC8IGckqKQjrjYjIvg=; b=CN7q+M3WGkdj0b0d9phn/eQ9VJEpIrYQPLBi29pvl2pg0qK8nrbpxW2a+5Afm2LfAC kYOKDC9q3UEgYWxWjBT5ox62lZ6oiko+/UuBQXcQAawBEQIk1l3w9KIU8VYywGOciesB faZgnRAXU0rHwdcq3wOY3wzgZUZo+/A+YXI8DQhAoPfothVsF7cVutdR/RXubTgCAD23 d6dFvtyvTU/cNj3LRBXfFITGdJ9fdGwx3mwsTHarWc81HQOr3qvb5LIsb4hNyb+D5/ej V2n+A2ds25LPLSfYbqooQQ21qsZH6lFExRGqWJc/1ivyTUaPIEo9BydnXhrSQIRPt/a5 kmoA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=d3E9ue+0; 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 w54si8208153eda.214.2019.10.28.09.00.48; Mon, 28 Oct 2019 09:01:14 -0700 (PDT) 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=d3E9ue+0; 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 S1729716AbfJ1GUu (ORCPT + 99 others); Mon, 28 Oct 2019 02:20:50 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:39260 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728657AbfJ1GUu (ORCPT ); Mon, 28 Oct 2019 02:20:50 -0400 Received: by mail-wr1-f68.google.com with SMTP id a11so8506323wra.6 for ; Sun, 27 Oct 2019 23:20:48 -0700 (PDT) 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=llIvbuQZkok97wxZ5YRzO3v5zhC8IGckqKQjrjYjIvg=; b=d3E9ue+06kHNnDqAASgZVQs/YYZm26QWcDV4BRilYMu3mXLeqlJpXcO7TsWL4VEC1B U5baMJLe2nuHQhhmLqbRt9G9bqGwExWe3GJQm0JQojFqw89YGNume05u6vLVAiVbqHmq KjSs5ceqISrnvxnkmEOQiEmR9LdMCwCjBV3D5cJFimAYkt8h0UOr7V+SNSG96E94rsX6 SlzEeXtmT9EgMqfBmvrAW4Ye1p/YOsxT44Q6L9xcxzLjwIUItSlJZas4NdtrdjQA5Wbr PNVipujcRYKFhyq7c67FPQfhJAwY7evKX2BS9edqjjkYql8kEk0vU2zm6XNzOfrUY9so fVTQ== 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=llIvbuQZkok97wxZ5YRzO3v5zhC8IGckqKQjrjYjIvg=; b=G4DFDS6e8Tux7H70CF7dDXWZSqgL3gZquqhvCNbL5hfPEcv+S3AM2hWJJZcDxCqB4n GPG341CkClwY1IymFIystrwiK8/JVNjF44/nV4C3aY0oVQHHTDaBOlbw1VysU2wgEo+a BX+nscx0RoLRwdYF0hoSik4GvbqCROWFmHs55xu8O7OFuOuaF2YQn34GNT+MDwjbr2Tp Ka2nxULTG1wkfDPl57UrzamviHBvObZw4QUjjOD48u8JGstgIlrF09hHIkQnUavOFSTI tKS+IwkncLsyWYfI9pE695n7oQBG8xdfKqoeT2ZauEiJPNgolyQJz1SBWZqGjz2jxFMX s45w== X-Gm-Message-State: APjAAAUuYycmaltztVupw7g6WvebbHcLg7lGsaeaKpOa00INp0u/TbTM SXv9zndLEly2RJrBBZ2lhXQrnYXyg3CXGFnMaqiIz9uPFWeZ2A== X-Received: by 2002:adf:8289:: with SMTP id 9mr14429527wrc.0.1572243647698; Sun, 27 Oct 2019 23:20:47 -0700 (PDT) MIME-Version: 1.0 References: <20191024132345.5236-1-ard.biesheuvel@linaro.org> <20191024132345.5236-25-ard.biesheuvel@linaro.org> <74d5c30d-d842-5bdb-ebb8-2aa47ffb5e8d@c-s.fr> In-Reply-To: From: Ard Biesheuvel Date: Mon, 28 Oct 2019 07:20:46 +0100 Message-ID: Subject: Re: [PATCH v2 24/27] crypto: talitos - switch to skcipher API To: Christophe Leroy Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Herbert Xu , "David S. Miller" , Eric Biggers , linux-arm-kernel 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 Sun, 27 Oct 2019 at 14:05, Christophe Leroy wr= ote: > > > > Le 27/10/2019 =C3=A0 12:05, Ard Biesheuvel a =C3=A9crit : > > On Sun, 27 Oct 2019 at 11:45, Christophe Leroy wrote: > >> > >> > >> > >> Le 24/10/2019 =C3=A0 15:23, Ard Biesheuvel a =C3=A9crit : > >>> Commit 7a7ffe65c8c5 ("crypto: skcipher - Add top-level skcipher inter= face") > >>> dated 20 august 2015 introduced the new skcipher API which is suppose= d to > >>> replace both blkcipher and ablkcipher. While all consumers of the API= have > >>> been converted long ago, some producers of the ablkcipher remain, for= cing > >>> us to keep the ablkcipher support routines alive, along with the matc= hing > >>> code to expose [a]blkciphers via the skcipher API. > >>> > >>> So switch this driver to the skcipher API, allowing us to finally dro= p the > >>> blkcipher code in the near future. > >>> > >>> Signed-off-by: Ard Biesheuvel > >> > >> With this series, I get the following Oops at boot: > >> > > > > Thanks for the report. > > > > Given that the series only modifies ablkcipher implementations, it is > > rather curious that the crash occurs in ahash_init(). Can you confirm > > that the crash does not occur with this patch reverted? > > Yes I confirm. > > You changed talitos_cra_init_ahash(). talitos_init_common() is not > called anymore. I think that's the reason. > Thanks a lot for digging into this Does this fix things for you? index c29f8c02ea05..d71d65846e47 100644 --- a/drivers/crypto/talitos.c +++ b/drivers/crypto/talitos.c @@ -3053,7 +3053,7 @@ static int talitos_cra_init_ahash(struct crypto_tfm *= tfm) crypto_ahash_set_reqsize(__crypto_ahash_cast(tfm), sizeof(struct talitos_ahash_req_ctx)); - return 0; + return talitos_init_common(ctx, talitos_alg); } static void talitos_cra_exit(struct crypto_tfm *tfm)