Make vm fork information available instead?

Posted Jul 5, 2024 15:24 UTC (Fri) by WolfWings (subscriber, #56790)
In reply to: Make vm fork information available instead? by donald.buczek
Parent article: Another try for getrandom() in the vDSO

Especially because it seems like they moved their proposal entirely out of random's purvue since they're not tracking reseeds but an entirely different and specific event, so I don't see why the NACK from random matters when it's no longer integrating with their subsystem?

Make vm fork information available instead?

Posted Jul 5, 2024 15:29 UTC (Fri) by bluca (subscriber, #118303) [Link] (1 responses)

Those are excellent questions. The issue is that the random subsystem maintainer also happens to the vmgenid acpi driver maintainer.

Make vm fork information available instead?

Posted Jul 5, 2024 15:32 UTC (Fri) by bluca (subscriber, #118303) [Link]

It is a very sad situation indeed, especially because in the end, even though it could be really trivially fixed, the result is that from that point of view, Windows works better as a VM guest than Linux.