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] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 8 Nov 2017 08:52:24 +1030
From:   Joel Stanley <joel@....id.au>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Michal Hocko <mhocko@...e.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Nov 7

Hello Michal,

On Tue, Nov 7, 2017 at 3:52 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20171106:
>
> The powerpc tree still had its build failure for which I applied a patch.
>
> The crypto tree lost its build failure.
>
> The akpm tree still had its build failure for which I reverted a commit.
>
> Non-merge commits (relative to Linus' tree): 10912
>  10165 files changed, 524042 insertions(+), 247066 deletions(-)

I tried to boot this -next tree built for the ARM platform I maintain,
and it did not make it to userspace. When I revert your patch
"fs/binfmt_elf.c: drop MAP_FIXED usage from elf_map" the system boots
as expected.

There are a lot of messages on the way up that look like this:

[    2.527460] Uhuuh, elf segement at 000d9000 requested but the
memory is mapped already
[    2.540160] Uhuuh, elf segement at 000d9000 requested but the
memory is mapped already
[    2.546153] Uhuuh, elf segement at 000d9000 requested but the
memory is mapped already

And then trying to run userspace looks like this:

 [    3.116476] Uhuuh, elf segement at 000d9000 requested but the
memory is mapped already
[    3.116988] Failed to execute /init (error -11)
[    3.117713] Starting init: /sbin/init exists but couldn't execute
it (error -14)
[    3.118879] Starting init: /bin/sh exists but couldn't execute it (error -14)
[    3.119186] Kernel panic - not syncing: No working init found.  Try
passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance.
[    3.119683] CPU: 0 PID: 1 Comm: init Not tainted
4.14.0-rc8-next-20171107-00016-g9f804d9fa870 #55
[    3.119933] Hardware name: Generic DT based system
[    3.120205] [<8000fa9c>] (unwind_backtrace) from [<8000d2dc>]
(show_stack+0x10/0x14)
[    3.120462] [<8000d2dc>] (show_stack) from [<800174bc>] (panic+0xb8/0x244)
[    3.120688] [<800174bc>] (panic) from [<80355298>] (kernel_init+0xc8/0xf0)
[    3.120880] [<80355298>] (kernel_init) from [<8000a5e0>]
(ret_from_fork+0x14/0x34)

I've built the aspeed_g5_defconfig, which is a 32 bit ARM machine. The
full dmesg is attached.

I noted a report of this for ppc64, but I'm not on that list:

 https://marc.info/?l=linuxppc-embedded&m=151005537413751&w=2

Cheers,

Joel

Download attachment "next-20171107-failure" of type "application/octet-stream" (14626 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ