linux-kernel - Re: [efi] 1c5fecb612: WARNING:at

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 5 Dec 2019 13:29:25 +0000
From:   <Narendra.K@...l.com>
To:     <rong.a.chen@...el.com>
CC:     <ard.biesheuvel@...aro.org>, <Mario.Limonciello@...l.com>,
        <linux-kernel@...r.kernel.org>, <torvalds@...ux-foundation.org>,
        <lkp@...ts.01.org>, <Narendra.K@...l.com>
Subject: Re: [efi] 1c5fecb612: WARNING:at_kernel/iomem.c:#memremap

On Tue, Dec 03, 2019 at 04:20:51PM +0800, Rong Chen wrote:
> On 12/2/19 5:41 PM, Ard Biesheuvel wrote:
> > On Sun, 1 Dec 2019 at 16:53, kernel test robot <rong.a.chen@...el.com> wrote:
> > > FYI, we noticed the following commit (built with gcc-7):
> > > 
> > > commit: 1c5fecb61255aa12a16c4c06335ab68979865914 ("efi: Export Runtime Configuration Interface table to sysfs")
> > > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> > > 
> > > in testcase: rcutorture
> > > with following parameters:
> > > 
> > >          runtime: 300s
> > >          test: default
> > >          torture_type: tasks
> > > 
> > > test-description: rcutorture is rcutorture kernel module load/unload test.
> > > test-url: https://www.kernel.org/doc/Documentation/RCU/torture.txt
> > > 
> > > 
> > > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
> > > 
> > > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> > > 
> > > 
> > > +------------------------------------------------+------------+------------+
> > > |                                                | 5828efb95b | 1c5fecb612 |
> > > +------------------------------------------------+------------+------------+
> > > | boot_successes                                 | 0          | 0          |
> > > | boot_failures                                  | 4          | 4          |
> > > | Kernel_panic-not_syncing:No_working_init_found | 4          | 4          |
> > > | WARNING:at_kernel/iomem.c:#memremap            | 0          | 4          |
> > > | EIP:memremap                                   | 0          | 4          |
> > > +------------------------------------------------+------------+------------+
> > > 
> > I don't understand this result. Doesn't it say the number of failures
> > is the same, but it just fails in a different place? Is there a
> > working config that breaks due to that commit?
> 
> Hi Ard,
> 
> The results means all boot are failed, parent commit fails at
> "Kernel_panic-not_syncing:No_working_init_found"
> which may causes by the wrong test environment, but the commit "1c5fecb612"
> introduced a new error:
> "WARNING:at_kernel/iomem.c:#memremap".
> 
> We prepared the reproduce steps and config file in report mail:
> https://lore.kernel.org/lkml/20191201155238.GR18573@shao2-debian/
> 

Hi Rong,

Thank you. I am trying to replicate the issue. I will share findings.

-- 
With regards,
Narendra K