The number is currently published by the vmgenid(4) driver and has no
"entropy," but should be integrated quickly on VM rewind events to avoid
duplicate sequences.
Details
Details
- Reviewers
whu markm jmg - Group Reviewers
csprng O3: Kernel Random Numbers Generator (Owns No Changed Paths) - Commits
- rS356245: vmgenid(4): Integrate as a random(4) source
(If we think the entropy would be more valuable, we could restrict
publication of the GUID from vmgenid(4). I do not know if it is available
to unprivileged users in any other way.)
Diff Detail
Diff Detail
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 28353 Build 26444: arc lint + arc unit