| 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
| ||
|
Message-Id: <20181030115507.GA29437@rapoport-lnx>
Date: Tue, 30 Oct 2018 13:55:08 +0200
From: Mike Rapoport <rppt@...ux.ibm.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: kernel test robot <rong.a.chen@...el.com>,
Mike Rapoport <rppt@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Michal Hocko <mhocko@...e.com>,
Catalin Marinas <catalin.marinas@....com>,
Chris Zankel <chris@...kel.net>,
"David S. Miller" <davem@...emloft.net>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Greentime Hu <green.hu@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Guan Xuetao <gxt@....edu.cn>, Ingo Molnar <mingo@...hat.com>,
"James E.J. Bottomley" <jejb@...isc-linux.org>,
Jonas Bonn <jonas@...thpole.se>,
Jonathan Corbet <corbet@....net>,
Ley Foon Tan <lftan@...era.com>,
Mark Salter <msalter@...hat.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Matt Turner <mattst88@...il.com>,
Michael Ellerman <mpe@...erman.id.au>,
Michal Simek <monstr@...str.eu>,
Palmer Dabbelt <palmer@...ive.com>,
Paul Burton <paul.burton@...s.com>,
Richard Kuo <rkuo@...eaurora.org>,
Richard Weinberger <richard@....at>,
Rich Felker <dalias@...c.org>,
Russell King <linux@...linux.org.uk>,
Serge Semin <fancer.lancer@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Tony Luck <tony.luck@...el.com>,
Vineet Gupta <vgupta@...opsys.com>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org
Subject: Re: [LKP] [mm] 68c37ccedc:
BUG:kernel_hang_in_early-boot_stage,last_printk:early_console_in_setup_code
On Mon, Oct 29, 2018 at 03:47:11PM -0700, Andrew Morton wrote:
> On Mon, 29 Oct 2018 21:15:01 +0800 kernel test robot <rong.a.chen@...el.com> wrote:
>
> > FYI, we noticed the following commit (built with gcc-7):
> >
> > commit: 68c37ccedcde10514898f4ba3b28c0de85c590d1 ("mm: nobootmem: remove bootmem allocation APIs")
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
> >
> > in testcase: boot
> >
> > on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 2G
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
> > +-----------------------------------------------------------------------------+------------+------------+
> > | | 6881a1e729 | 68c37ccedc |
> > +-----------------------------------------------------------------------------+------------+------------+
> > | boot_successes | 4 | 0 |
> > | boot_failures | 0 | 4 |
> > | BUG:kernel_hang_in_early-boot_stage,last_printk:early_console_in_setup_code | 0 | 4 |
> > +-----------------------------------------------------------------------------+------------+------------+
>
> Well that's irritating.
>
> Does the problem remain when the entire patch series is applied?
There is no more commit 68c37ccedcde in linux-next, so I've tried to
reproduce with next-20181029 and the attached .config. I've also checked
commit "mm: nobootmem: remove bootmem allocation APIs" in the yesterday's
linux-next.
Both are booting just fine on my machine.
I've built the kernel with gcc 5.4.0 (Ubuntu) and gcc 7.3.0 (Debian).
> mm-remove-config_no_bootmem.patch
> mm-remove-config_no_bootmem-fix.patch
> mm-remove-config_have_memblock.patch
> mm-remove-config_have_memblock-fix.patch
> mm-remove-config_have_memblock-fix-2.patch
> mm-remove-config_have_memblock-fix-3.patch
> mm-remove-bootmem-allocator-implementation.patch
> mm-nobootmem-remove-dead-code.patch
> memblock-rename-memblock_alloc_nid_try_nid-to-memblock_phys_alloc.patch
> memblock-remove-_virt-from-apis-returning-virtual-address.patch
> memblock-replace-alloc_bootmem_align-with-memblock_alloc.patch
> memblock-replace-alloc_bootmem_low-with-memblock_alloc_low.patch
> memblock-replace-__alloc_bootmem_node_nopanic-with-memblock_alloc_try_nid_nopanic.patch
> memblock-replace-alloc_bootmem_pages_nopanic-with-memblock_alloc_nopanic.patch
> memblock-replace-alloc_bootmem_low-with-memblock_alloc_low-2.patch
> memblock-replace-__alloc_bootmem_nopanic-with-memblock_alloc_from_nopanic.patch
> memblock-add-align-parameter-to-memblock_alloc_node.patch
> memblock-replace-alloc_bootmem_pages_node-with-memblock_alloc_node.patch
> memblock-replace-__alloc_bootmem_node-with-appropriate-memblock_-api.patch
> memblock-replace-alloc_bootmem_node-with-memblock_alloc_node.patch
> memblock-replace-alloc_bootmem_low_pages-with-memblock_alloc_low.patch
> memblock-replace-alloc_bootmem_pages-with-memblock_alloc.patch
> memblock-replace-__alloc_bootmem-with-memblock_alloc_from.patch
> memblock-replace-alloc_bootmem-with-memblock_alloc.patch
> mm-nobootmem-remove-bootmem-allocation-apis.patch
> memblock-replace-free_bootmem_node-with-memblock_free.patch
> memblock-replace-free_bootmem_late-with-memblock_free_late.patch
> memblock-rename-free_all_bootmem-to-memblock_free_all.patch
> memblock-rename-__free_pages_bootmem-to-memblock_free_pages.patch
> mm-remove-nobootmem.patch
> memblock-replace-bootmem_alloc_-with-memblock-variants.patch
> mm-remove-include-linux-bootmemh.patch
> mm-remove-include-linux-bootmemh-fix.patch
> mm-remove-include-linux-bootmemh-fix-2.patch
> mm-remove-include-linux-bootmemh-fix-3.patch
> docs-boot-time-mm-remove-bootmem-documentation.patch
>
--
Sincerely yours,
Mike.
Powered by blists - more mailing lists