Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3103374pxk; Mon, 5 Oct 2020 00:46:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzLYR0A/pelepEbxSgEh9MIwGJkkJZs/gevGBjc/1IvaK1lS1RbtDbLKywcKpcHVddEhpKu X-Received: by 2002:a17:906:c0d0:: with SMTP id bn16mr14141113ejb.279.1601883977393; Mon, 05 Oct 2020 00:46:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601883977; cv=none; d=google.com; s=arc-20160816; b=jLZ9eNwg9zFg7pWVIusvBVnMZYr/gCymDcVOhIwA0NGYLp5XoKwa9sAav5eCM0Sv8L Qo5wFUihYDcQJGwAigWzMGZbsRAKMCv64duvoeZ9BWcw5k6/ByeB2xGyDAdDWw8MXJRc DzShHca9hEDYE0iasnDgwPggAxkUVRA8suhCQ6DHKRBDz2MWIYpm4+/s3kNjARrjpFQZ f0EsTwPUzvK2/2bZ3iZ4pQiGugeCH0Mohv0jPEvbnS8JRU7FjZTj2LzWBKg4QFSpYh2r MPxkPh7ZOZm2iSpOwG2jIEO1eR4bvc4EKC0L7b9ufETyyCA06EK2kRfFS4gNZMLeKxlt PEIQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=JI6A9PpIQFNnYPSlFbk1aFwk9N6qbShlSuz0WnZt37Q=; b=iht8fWgNtmLeInfgXwZw0BQ1eUcEdTogeuO/Y0EGChWVsGtGgwDjryLcOwqskduhYh lWZsM+EuxJzTj5uQfLyP813xkDLfyOyy3MmkO3VsvE5RoziNHBNeUyKJX7LDC3kIl+C5 bqhxxB+C+9De1KR1XyTOWSxkh7hRour4AYjwvTP9jVcFvonYCygqDA9MJGHgZvVSI50q aZBaOnT0pKNLdt3XbHpLbdnJSr3bGlqoMQIqUIFhpJT8t1LEpOZjh4bgfaKRFq7HXw5J QdGoth+rZ0pEIy5nPHDTWEzWRYX7t33zC0fyYqbi/e67WsajOsNmkCqD4snCXvgk4zu/ jHdQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chronox.de header.s=strato-dkim-0002 header.b=U3oczptI; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j24si7002376ejb.48.2020.10.05.00.45.43; Mon, 05 Oct 2020 00:46:17 -0700 (PDT) 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=@chronox.de header.s=strato-dkim-0002 header.b=U3oczptI; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725880AbgJEHpk (ORCPT + 99 others); Mon, 5 Oct 2020 03:45:40 -0400 Received: from mo4-p01-ob.smtp.rzone.de ([85.215.255.54]:29209 "EHLO mo4-p01-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725870AbgJEHpk (ORCPT ); Mon, 5 Oct 2020 03:45:40 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1601883938; s=strato-dkim-0002; d=chronox.de; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=JI6A9PpIQFNnYPSlFbk1aFwk9N6qbShlSuz0WnZt37Q=; b=U3oczptIrcqNUK/Sdc39uV2WTuCkl8Yzic2rXHSG3LotVotGo4uRjMOcrlWLikPrn8 uQZkmh67FdzT516GT/0vcni/3EZ1OHvwWLaUrBm7hz8Q/XE16SO75g/xos71SQ3nHYkX w1WvdpxuOqG4Fo4WQcDdfs3PS+d0F92bG/KcFzx5KVgOQLa9SpgbxZ2qBYESFLGW0ZWB LAYljgxJF19kaMeOfJzAnL6W2DZQFT4zr5d16bAholY3o4Le+NEDDgPh9A9vi3syzUP3 JCnXNzkHeF2vVTRWGKLU8K80SEHPLzGNy50nmu/AxX3zKZuv3mlbMP4s0rie3JHdChFK jL2A== X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9xmwdNnzGHXPZJfSYkOI=" X-RZG-CLASS-ID: mo00 Received: from tauon.chronox.de by smtp.strato.de (RZmta 47.2.1 DYNA|AUTH) with ESMTPSA id C0b627w957jYBRk (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Mon, 5 Oct 2020 09:45:34 +0200 (CEST) From: Stephan Mueller To: Ard Biesheuvel Cc: Christoph Hellwig , Palmer Dabbelt , linux-riscv , Android Kernel Team , kernel test robot , Linux Crypto Mailing List , Linux Kernel Mailing List Subject: Re: [PATCH] crypto: jitterentropy - bind statically into kernel Date: Mon, 05 Oct 2020 09:45:33 +0200 Message-ID: <2961600.L5xXbe6F5v@tauon.chronox.de> In-Reply-To: References: <20200930065617.934638-1-palmerdabbelt@google.com> <2588700.mWSkj6HvKX@tauon.chronox.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Am Montag, 5. Oktober 2020, 08:44:39 CEST schrieb Ard Biesheuvel: Hi Ard, > On Mon, 5 Oct 2020 at 08:40, Stephan Mueller wrote: > > Am Montag, 5. Oktober 2020, 08:24:46 CEST schrieb Ard Biesheuvel: > > > > Hi Ard, > > > > > If jitterentropy is a special case, we could put a alternate > > > non-'static inline' version of random_get_entropy() in the core > > > kernel, and only export it if JITTER_ENTROPY is built as a module in > > > the first place. But I'd prefer it if jitterentropy switches to an API > > > that is suitable for driver consumption. > > > > Which API do you have in mind? In user space, I use > > clock_gettime(CLOCK_REALTIME) which also considers the clock source. > > AFAICT, that call is backed by ktime_get_real_ts64(), which is already > being exported to modules. > > Could you please check whether that works for your driver? Yes, will do. Thanks. Ciao Stephan