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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 19 Jun 2018 10:08:30 +0200
From:   Peter Zijlstra <>
To:     Alan Cox <>
Cc:     Sergey Senozhatsky <>,
        Petr Mladek <>,
        Steven Rostedt <>,
        Greg Kroah-Hartman <>,
        Jiri Slaby <>,
        Linus Torvalds <>,
        Andrew Morton <>,
        Dmitry Vyukov <>,,,
        Sergey Senozhatsky <>
Subject: Re: [RFC][PATCH 0/6] Use printk_safe context for TTY and UART port

On Mon, Jun 18, 2018 at 02:38:18PM +0100, Alan Cox wrote:
> Given printk nowdays is already somewhat unreliable with all the perf
> related changes,

printk is a steaming pile of @#$#@, unreliable doesn't even begin to
cover it.

> and we have other good debug tools

What other good debug tools do you have? The only thing I have that
actually works is earlyser/8250_early -- and I route everything printk
into that.

Powered by blists - more mailing lists