Sorry Jann for missing your original email. On 27/11/2020 20:22, Jann Horn wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. > > > > [resend in the hope that amazon will accept my mail this time instead > of replying "550 Too many invalid recipients" again] > > On Fri, Nov 20, 2020 at 11:29 PM Jann Horn <jannh@xxxxxxxxxx> wrote: >> On Mon, Nov 16, 2020 at 4:35 PM Catangiu, Adrian Costin >> <acatan@xxxxxxxxxx> wrote: >>> This patch is a driver that exposes a monotonic incremental Virtual >>> Machine Generation u32 counter via a char-dev FS interface that >>> provides sync and async VmGen counter updates notifications. It also >>> provides VmGen counter retrieval and confirmation mechanisms. >>> >>> The hw provided UUID is not exposed to userspace, it is internally >>> used by the driver to keep accounting for the exposed VmGen counter. >>> The counter starts from zero when the driver is initialized and >>> monotonically increments every time the hw UUID changes (the VM >>> generation changes). >>> >>> On each hw UUID change, the new hypervisor-provided UUID is also fed >>> to the kernel RNG. >> As for v1: >> >> Is there a reasonable usecase for the "confirmation" mechanism? It >> doesn't seem very useful to me. I think it adds value in complex scenarios with multiple users of the mechanism, potentially at varying layers of the stack, different processes and/or runtime libraries. The driver offers a natural place to handle minimal orchestration support and offer visibility in system-wide status. A high-level service that trusts all system components to properly use the confirmation mechanism can actually block and wait patiently for the system to adjust to the new world. Even if it doesn't trust all components it can still do a best-effort, timeout block. >> >> How do you envision integrating this with libraries that have to work >> in restrictive seccomp sandboxes? If this was in the vDSO, that would >> be much easier. Since this mechanism targets all of userspace stack, the usecase greatly vary. I doubt we can have a single silver bullet interface. For example, the mmap interface targets user space RNGs, where as fast and as race free as possible is key. But there also higher level applications that don't manage their own memory or don't have access to low-level primitives so they can't use the mmap or even vDSO interfaces. That's what the rest of the logic is there for, the read+poll interface and all of the orchestration logic. Like you correctly point out, there are also scenarios like tight seccomp jails where even the FS interfaces is inaccessible. For cases like this and others, I believe we will have to work incrementally to build up the interface diversity to cater to all the user scenarios diversity. Thanks, Adrian. Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
