On Tue, Feb 11, 2020 at 02:47:05PM -0800, Andy Lutomirski wrote: > On Tue, Feb 11, 2020 at 5:53 AM Joerg Roedel <joro@xxxxxxxxxx> wrote: > > > > From: Joerg Roedel <jroedel@xxxxxxx> > > > > Send SIGBUS to the user-space process that caused the #VC exception > > instead of killing the machine. Also ratelimit the error messages so > > that user-space can't flood the kernel log. > > What would cause this? CPUID? Something else? Yes, CPUID, RDTSC(P) and, most importantly, user-space mapping some IO space an accessing it, causing MMIO #VC exceptions. Especially the MMIO case has so many implications that it will not be supported at the moment. Imagine for example MMIO accesses by 32bit user-space with non-standard, non-zero based code and data segments. Or user-space changing the instruction bytes between when the #VC exception is raised and when the handler parses the instruction. Lots of checks are needed to make this work securely, and the complexity of this is not worth it at this time. Regards, Joerg _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
