On Fri, Sep 06, 2019 at 01:02:21PM +0200, Jean Delvare wrote: > I've been bitten recently by mcelog not working on machines started in > secure boot mode. mcelog tries to read DMI information from /dev/mem > and fails to open it.
What do you mean by "secure boot"? Is this matthew's patchset that restricts /dev/mem/ or something else? > This made me wonder: if not even root can read /dev/mem (nor, I > suppose, /dev/kmem and /dev/port) in secure boot mode, why are we > creating these device nodes at all in the first place? Can't we detect > that we are in secure boot mode and skip that step, and reap the rewards > (faster boot, lower memory footprint and less confusion)? Sure, feel free to not register it at all if the mode is enabled. thanks, greg k-h
