linux-kernel - Re: [PATCH 0/3] printk: Add force_early

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]

Message-ID: <20170928160230.GA606@tigerII.localdomain>
Date:   Fri, 29 Sep 2017 01:02:30 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     pmladek@...e.com, sergey.senozhatsky@...il.com,
        linux-kernel@...r.kernel.org, rostedt@...dmis.org,
        mingo@...nel.org, tglx@...utronix.de
Subject: Re: [PATCH 0/3] printk: Add force_early_printk boot param

On (09/28/17 14:18), Peter Zijlstra wrote:
> Most all printk() bits are terminally broken because they rely on the scheduler
> and blocking locks to function, making them unsuitable for debugging the
> scheduler and NMI context things.

hold on... wait a second... the scheduler is not lockless yet? darn...

ok, I think having something like that in printk.c wouldn't hurt. Petr
was going to take a look, IIRC.

but what's up with that scheduler thing I keep hearing about, must be
something new, can I disable it in kconfig? it seems to be conflicting
with CONFIG_PRINTK.

	-ss