Messages in this thread | | | Date | Sun, 25 Jun 2017 15:31:49 +0200 | From | Greg KH <> | Subject | Re: [RFC] memory corruption caused by efi driver? |
| |
On Sun, Jun 25, 2017 at 09:06:58PM +0800, Xishi Qiu wrote: > On 2017/6/24 19:12, Greg KH wrote: > > > On Sat, Jun 24, 2017 at 05:52:23PM +0800, Yisheng Xie wrote: > >> hi all, > >> > >> I met an Oops problem with linux-3.10. The RIP is sysfs_open_file+0x46/0x2b0 (I will and the full > >> crash log in the end of this mail). > > > > 3.10 is _very_ old and obsolete, can you duplicate this on a modern > > kernel, like 4.11? > > > > thanks, > > > > greg k-h > > > > . > > > > Hi, if I disable CONFIG_EFI_VARS, it seems OK now. > > And I cann't reproduce the problem on mainline(v4.12). > > Here is my test, run some stress test, then > cat /sys/firmware/efi/efivars/* > or > cat /sys/firmware/efi/vars/*/* > > 1) 3.10, get warning > CONFIG_EFI_VARS=y > CONFIG_EFIVAR_FS=y > > 2) 3.10, get warning > CONFIG_EFI_VARS=y > CONFIG_EFIVAR_FS=n > > 3) 3.10, ok > CONFIG_EFI_VARS=n > CONFIG_EFIVAR_FS=y > > 4) mainline, ok > CONFIG_EFI_VARS=y > CONFIG_EFIVAR_FS=y
Then use mainline :)
| |