On Sun, 14 Sep, at 02:01:30AM, Borislav Petkov wrote: > On Sat, Sep 13, 2014 at 11:36:16AM -0700, Ricardo Neri wrote: > > Being more verbose about this kind of illegal access from the firmware > > increases the likelihood of this kind firmware bugs to be fixed. > > I sincerely hope you're right and, more importantly, how do we make sure > those warnings get seen in time for a fix to even be possible..? Some firmware teams do run Linux as part of their validation process, and have been known to pay attention to the kernel boot messages. So there's definitely hope there. But we are also taking a more active approach with the Linux UEFI Validation project [1], where we consume these kinds of error messages and turn them into explicit test passes/failures. We've been attending the UEFI plugfests and trying to work directly with firmware engineers to bridge that communication gap between firmware and OS, so that we can fix these kinds of bugs before they appear in the wild. [1] - https://01.org/linux-uefi-validation -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
