Re: [RFC] memory corruption caused by efi driver?

From	Greg KH <gregkh@linuxfoundation.org>
Newsgroups	linux.kernel
Subject	Re: [RFC] memory corruption caused by efi driver?
Date	2017-06-25 15:40 +0200
Message-ID	<tWfVD-5G2-1@gated-at.bofh.it> (permalink)
References	<tVQ1b-6d5-5@gated-at.bofh.it> <tVRgB-778-3@gated-at.bofh.it> <tWfsC-5ve-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

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 :)

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[RFC] memory corruption caused by efi driver? Yisheng Xie <xieyisheng1@huawei.com> - 2017-06-24 12:00 +0200
  Re: [RFC] memory corruption caused by efi driver? Greg KH <gregkh@linuxfoundation.org> - 2017-06-24 13:20 +0200
    Re: [RFC] memory corruption caused by efi driver? Xishi Qiu <qiuxishi@huawei.com> - 2017-06-25 15:10 +0200
      Re: [RFC] memory corruption caused by efi driver? Greg KH <gregkh@linuxfoundation.org> - 2017-06-25 15:40 +0200

csiph-web