Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp2735315pxb; Mon, 31 Jan 2022 03:12:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJzBRGdoy7vzVXWzj5vJGg0+PBwKgU4nd/JW6AESlUtl1gw3HKdBV3AU2rj1USV6ddGW1Yuk X-Received: by 2002:a63:fe42:: with SMTP id x2mr16352700pgj.334.1643627563371; Mon, 31 Jan 2022 03:12:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643627563; cv=none; d=google.com; s=arc-20160816; b=TaP4iUQbt4QQY897lwrYWHt0lv+cfFkL5gHWJBMjSBqM8FKtX2XAYd4EP9VIpq5v+2 YrSsp81IZdHxnse2yBtkxZFRHQYperMVAkTqhu/o51XXQ4Owey2MnVoMkljmampsQd6f DojnBg0GW/Uo0FcKkbZ2KCs69ogKA6z8kKm73kJRtbgpvm0inkPU9u1823jL3AFIkKLc 29oNLSlT0kI4CDJOCRyY1xGObz+euHFvozTroQndgemduqamsq5Cm9KRs/Z30lGXx0s2 9bXE/LKpEUPA4F+uB0lLf1wpL8EMQ4sJ5XRLPYJw2HWYbymtkczEPADZSAkURrt3v73d D31Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-disposition:mime-version:message-id :subject:cc:to:from:date:dkim-signature; bh=OITQFSeLoNTaXoQED/aKEaT2kE+25ScYSreXKHuTHfA=; b=ldWEtcgtA13VCR+sm++ycQbDNSs0TM9aUkKLJ1Y3O/snq8Mm42WlufBAJuEtEKXqR4 IIiO2YCpeRLnDqWT6OKcNwPBBveds/L+InPoBlv5X//RRoO/3BEpqxaNdPp3Xr6Khj6m K2726+WhVcgCtNgfQov61/GULBPuvEIvH8zAUhKcNXxQbSrrozCkJHCFR3791WsCTT9s dYvyYoZ9nXeiSKFGfkFyrw5eT6Vu9FwwKCB6rlwVnq7O/5lcUe4aAhnoCg9qZ3nJSY3U dB5aCPTnvcdlIIwYRWzSu1yyPDfLhg+z4CTBvb0haNaKZxeZgyOm3yVAulwGyMpmKFJ4 MEBA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@pqgruber.com header.s=mail header.b=NbBf9e9r; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=pqgruber.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t11si4006401pga.410.2022.01.31.03.12.29; Mon, 31 Jan 2022 03:12:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@pqgruber.com header.s=mail header.b=NbBf9e9r; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=pqgruber.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232937AbiA1Pie (ORCPT + 99 others); Fri, 28 Jan 2022 10:38:34 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59112 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231320AbiA1Pie (ORCPT ); Fri, 28 Jan 2022 10:38:34 -0500 X-Greylist: delayed 327 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Fri, 28 Jan 2022 07:38:33 PST Received: from mail.pqgruber.com (mail.pqgruber.com [IPv6:2a05:d014:575:f70b:4f2c:8f1d:40c4:b13e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B8100C061714 for ; Fri, 28 Jan 2022 07:38:33 -0800 (PST) Received: from workstation (213-47-165-233.cable.dynamic.surfer.at [213.47.165.233]) by mail.pqgruber.com (Postfix) with ESMTPSA id 7FE7CC2FBA4; Fri, 28 Jan 2022 16:33:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pqgruber.com; s=mail; t=1643383984; bh=OITQFSeLoNTaXoQED/aKEaT2kE+25ScYSreXKHuTHfA=; h=Date:From:To:Cc:Subject:From; b=NbBf9e9rpPTm5HzXRBIwqfgxKRXpJXS3lroGug11DjQGS+/0o1GYLaP/+TwLDn9cd UueeXefUgAJHk1RhWYmbF6B9HpZ159DcyG5H5YCgS11nY29AGMTWGhqfnq80omiudv KP9B0c2DBPLS635qUi/LWIGxwZ+6qxZmRD3x/MwI= Date: Fri, 28 Jan 2022 16:33:00 +0100 From: Clemens Gruber To: linux-crypto@vger.kernel.org Cc: Andrey Smirnov , Andrei Botila , Horia =?utf-8?Q?Geant=C4=83?= , linux-imx@nxp.com Subject: caam: Possible caam-rng regression since enabling prediction resistance Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi, I noticed that /dev/hwrng blocks indefinitely on our i.MX6Q (rev1.6) boards in recent kernel versions. As it did work before, I ran git bisect and found that reverting the following commit fixes the issue: 358ba762d9f1 ("crypto: caam - enable prediction resistance in HRWNG") cat /dev/hwrng | rngtest looks good on Linux 5.15 with aforementioned commit reverted. U-Boot version is 2021.07 and the RNG is not instantiated there. Any ideas what the problem could be with that commit and did you test the changes on i.MX6 devices? Let me know if you need more information / debug output / etc. Best regards, Clemens