Re:Uniting the Linux random-number devices
by Denvercoder9 on Wednesday December 20, 2023 @04:41PM
(#38714002)
A bit later another commit [1] was merged that makes reads from /dev/urandom opportunistically initialize the RNG. In practice this has the same result as the reverted commit on non-obsolete architectures, which support the jitter entropy generation.
[1] https://github.com/torvalds/linux/commit/48bff1053c172e6c7f3...
Re:Uniting the Linux random-number devices
by GoblinSlayer on Thursday December 21, 2023 @03:36AM
(#38718246)
On demand initialization? What a surprise.
Re:Uniting the Linux random-number devices
by influx on Wednesday December 20, 2023 @02:24PM
(#38712517)
Thanks for this, I'd been going off the previous articles on this, and hadn't realized it had been reverted.
Re:Uniting the Linux random-number devices
by rdtsc on Wednesday December 20, 2023 @03:34PM
(#38713276)
No problem. Thanks for finding and posting the article! The change was a good idea but like things happen, corner cases intervened.
[1] https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50a... [2] https://github.com/torvalds/linux/commit/0313bc278dac7cd9ce8...
> "This causes a large number of qemu boot test failures for various architectures (arm, m68k, microblaze, sparc32, xtensa are the ones I observed). Common denominator is that boot hangs at 'Saving random seed:'" This isn't hugely unexpected - we tried it, it failed, so now we'll revert it.