Messages in this thread | | | Date | Mon, 5 Oct 2020 07:56:44 +0100 | From | Christoph Hellwig <> | Subject | Re: [PATCH] crypto: jitterentropy - bind statically into kernel |
| |
On Mon, Oct 05, 2020 at 08:44:39AM +0200, Ard Biesheuvel wrote: > On Mon, 5 Oct 2020 at 08:40, Stephan Mueller <smueller@chronox.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.
Indeed. No need for my earlier idea..
| |