linux-kernel - problem w/ kernel init (rootfs vs initial console / init process)

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-next>] [day] [month] [year] [list]

Message-ID: <ed912df6-390f-989f-1ddc-7759a2989141@gmx.de>
Date:   Sun, 10 Sep 2017 11:09:21 +0200
From:   mtx <metux@....de>
To:     linux-kernel@...r.kernel.org
Subject: problem w/ kernel init (rootfs vs initial console / init process)

Hi folks,

I've got a very strange problem w/ v4.13 (on imx6):

it tries to open the initial console, before even attempt to mount the
root fs, which obviously is doomed to fail. (directly passing root=
via cmdline - no initrd etc)

What puzzles me most: prepare_namespace() is only called from
kernel_init_freeable() - after it tried to open console (only when no
ramdisk_execute_command found).

Anyone have an idea what could be wrong here ?

--mtx