Skip to contentSkip to conversation

rng-tools: Revert "rng-tools: move to meta-oe"

PATCH Randy MacLeod 1 participant 1 message Jan 18, 2024 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Sorry for the noise and back and forth on rng-tools removal. I'll avoid hastily cleaning up things for a while! ;-)

Quoted 4 lines · Randy MacLeod via lists.openembedded.org

From: Randy MacLeod<[email protected]>

This reverts commit d2b445384da3f3e6dab8577b6c56648b5244a788.

Quoted 8 lines

Revert this commit since:

- some systems using oe-core master may still be using kernels from before 5.6 pulled in the rng-tools algorithm, and

- some hardware platforms may not have a hardware random number generator and could therefore need to run rngd to avoid long boot-time initialization due to a depleted entropy pool.

The additional context that doesn't belong in the commit log
is that we talked about this change in the YP bug review meeting and decided that we would keep rng-tools in oe-core for 5.0-M2
for the two reasons given above. If we end up adding a test, as described below, we may never move the recipe to meta-oe.

It seems to me that we need a test that checks if the entropy pool size ever falls below a critical threshold for "too long" in the first N seconds of boot time.

Getting that test written so that:
 - qemu VMs and
 - real HW with and without /dev/hwrng

all pass without the test being too permissive may take some time.

I've created a bug to track adding such a test:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15360

Scott,
Do you have any info on the need for rngd on HW without /dev/hwrng but with a kernel >= 5.6 ?

../Randy