3 ms·
The commit [1] was eventually reverted [2] [1] https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50aedb39fb761567969865fe https://github.com/torvalds/li
by rdtsc 3y ago
The commit [1] was eventually reverted [2]
[1] https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50aedb39fb761567969865fe https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50a...
[2] https://github.com/torvalds/linux/commit/0313bc278dac7cd9ce83a8d384581dc043156965 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.
- influx 3y agoThanks for this, I'd been going off the previous articles on this, and hadn't realized it had been reverted.
- rdtsc 3y agoNo problem. Thanks for finding and posting the article! The change was a good idea but like things happen, corner cases intervened.
- Denvercoder9 3y agoA 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/48bff1053c172e6c7f340e506027d118147c8b7f https://github.com/torvalds/linux/commit/48bff1053c172e6c7f3...
- GoblinSlayer 3y agoOn demand initialization? What a surprise.
- minedwiz 3y ago`rdtsc`, you have a very appropriate username for the topic
- rdtsc 3y agoHa! You’re right.