[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2961600.L5xXbe6F5v@tauon.chronox.de>
Date: Mon, 05 Oct 2020 09:45:33 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>,
Palmer Dabbelt <palmerdabbelt@...gle.com>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Android Kernel Team <kernel-team@...roid.com>,
kernel test robot <lkp@...el.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] crypto: jitterentropy - bind statically into kernel
Am Montag, 5. Oktober 2020, 08:44:39 CEST schrieb Ard Biesheuvel:
Hi Ard,
> On Mon, 5 Oct 2020 at 08:40, Stephan Mueller <smueller@...onox.de> 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
Powered by blists - more mailing lists