Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4467261ybi; Tue, 11 Jun 2019 07:09:25 -0700 (PDT) X-Google-Smtp-Source: APXvYqzcGd905xtty3YfGw/8NsMbubaVGEAZDbLi1ZEoc/FH0Jx9ZAA5k+mr9hpBCln8y68oZvvV X-Received: by 2002:a17:902:30a3:: with SMTP id v32mr76994117plb.6.1560262165756; Tue, 11 Jun 2019 07:09:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560262165; cv=none; d=google.com; s=arc-20160816; b=XmGVLtXqzcJiODvQOyJFAgiJ79zK2PtCpfk008G+ZP/Ki7AusWYMHrcXd1oJpvd7Xs 764APsgqEpoBmEZpggWN31EAjs/ktLm7DRubGC94on3FVMrvJkUYzvtijNbKozPEy5z0 6ezNLgqbTE3n5c+IQJXEjBBggP7r3IVCoWq/j7+s89XdIVL3OvITnabcgMjbmQzEIrLf T38L3AEivI/JQk6DcOuDp0h4/tySfJUe8hAiwhG8g6ZKP5OP8GApd/E8s12b9Jcj07Tc P+qSNsiZKoD1o8RUCih6ZbwXSnxNPSDOcU1p7bRjyX2xWpLv7YVfPexoF7uViBJ2VaHk hHJw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=cGzgpxbRFlxcK7aezB5YmRNBHzKIp4lffWmjax6sgQQ=; b=hbj6Jcbw4LEzI9NTVm8DoASy5l687WM14aQMOoteHga2NVwYJLeuMcNjViNbXmx619 /xeWNEVHhX2apXWj2fFSCFWvuyqr1/YqeRMHT4lvvl7YIWYuXC9Y2nKQlEgrsNarbFcK hDu34ZVvA53YzE0o5ZwpAlKL2CrYbXv9y9JuwT3WZ9L1l8cwELoQHdbUUFmutS3H6UxF SrOO3DAY42nF7gBwl0o7T0J2sKJh5nduiCoT28YgfTFY4U3skqqFjaw8NVnS45JNv452 MNvXyO81HMN00hLdrUSj930lTHpMip1KC1KZmV79Y/crNJkfgW4uCNDIvwscf7HlS6cm vkDg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@c-s.fr header.s=mail header.b=WnDvxfK7; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j24si12401755pll.388.2019.06.11.07.09.10; Tue, 11 Jun 2019 07:09:25 -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=@c-s.fr header.s=mail header.b=WnDvxfK7; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387447AbfFKOE1 (ORCPT + 99 others); Tue, 11 Jun 2019 10:04:27 -0400 Received: from pegase1.c-s.fr ([93.17.236.30]:12504 "EHLO pegase1.c-s.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725811AbfFKOE0 (ORCPT ); Tue, 11 Jun 2019 10:04:26 -0400 Received: from localhost (mailhub1-int [192.168.12.234]) by localhost (Postfix) with ESMTP id 45NWvp6z72z9v0F4; Tue, 11 Jun 2019 16:04:22 +0200 (CEST) Authentication-Results: localhost; dkim=pass reason="1024-bit key; insecure key" header.d=c-s.fr header.i=@c-s.fr header.b=WnDvxfK7; dkim-adsp=pass; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at c-s.fr Received: from pegase1.c-s.fr ([192.168.12.234]) by localhost (pegase1.c-s.fr [192.168.12.234]) (amavisd-new, port 10024) with ESMTP id eCIThnGPA5aS; Tue, 11 Jun 2019 16:04:22 +0200 (CEST) Received: from messagerie.si.c-s.fr (messagerie.si.c-s.fr [192.168.25.192]) by pegase1.c-s.fr (Postfix) with ESMTP id 45NWvp5vKxz9v0F1; Tue, 11 Jun 2019 16:04:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c-s.fr; s=mail; t=1560261862; bh=cGzgpxbRFlxcK7aezB5YmRNBHzKIp4lffWmjax6sgQQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WnDvxfK7qGDC5nYHUZHAeW++MRre0DOZm+yuvmuDl/P2IoU6/KuJAQhcgGcYuoS7N 4MeefWV1hW8ekZlvU298lOyL/M5/hJ4e+O20Mqwcn/b2O9dJzp7ZXbUtJUydV06agi FzRUO1pqSJrLK7eCfM8hHv5yPSO6KudmKabLhTJY= Received: from localhost (localhost [127.0.0.1]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 485F98B7F4; Tue, 11 Jun 2019 16:04:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at c-s.fr Received: from messagerie.si.c-s.fr ([127.0.0.1]) by localhost (messagerie.si.c-s.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id z-vV47D7T_jZ; Tue, 11 Jun 2019 16:04:24 +0200 (CEST) Received: from PO15451 (unknown [192.168.4.90]) by messagerie.si.c-s.fr (Postfix) with ESMTP id 934918B75B; Tue, 11 Jun 2019 16:04:23 +0200 (CEST) Subject: Re: [PATCH v1 1/5] crypto: talitos - fix ECB and CBC algs ivsize To: Horia Geanta , Herbert Xu , "David S. Miller" Cc: "linux-crypto@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linuxppc-dev@lists.ozlabs.org" References: From: Christophe Leroy Message-ID: Date: Tue, 11 Jun 2019 16:04:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Le 11/06/2019 à 13:52, Horia Geanta a écrit : > On 6/6/2019 2:31 PM, Christophe Leroy wrote: >> commit d84cc9c9524e ("crypto: talitos - fix ECB algs ivsize") >> wrongly modified CBC algs ivsize instead of ECB aggs ivsize. >> >> This restore the CBC algs original ivsize of removes ECB's ones. >> >> Signed-off-by: Christophe Leroy >> Fixes: d84cc9c9524e ("crypto: talitos - fix ECB algs ivsize") > Initial patch is correct: > > $ git show -U10 d84cc9c9524e > [...] > @@ -2802,21 +2802,20 @@ static struct talitos_alg_template driver_algs[] = { > { .type = CRYPTO_ALG_TYPE_ABLKCIPHER, > .alg.crypto = { > .cra_name = "ecb(aes)", > .cra_driver_name = "ecb-aes-talitos", > .cra_blocksize = AES_BLOCK_SIZE, > .cra_flags = CRYPTO_ALG_TYPE_ABLKCIPHER | > CRYPTO_ALG_ASYNC, > .cra_ablkcipher = { > .min_keysize = AES_MIN_KEY_SIZE, > .max_keysize = AES_MAX_KEY_SIZE, > - .ivsize = AES_BLOCK_SIZE, > .setkey = ablkcipher_aes_setkey, > } > }, > [...] > > and similar for ecb(des), ecb(des3_ede). > > Current patch is incorrect: it adds ivsize for ecb and removes it from cbc. Very strange. Looks like there has been some rebase weirdness which have applied the patch on the wrong block at some point on my side, probably due to the fact that both blocks have the two previous and following lines identical. I've now rebased my serie on cryptodev/master and have the same behaviour as you. I'll resend the series without this patch. Christophe > > Horia >