linux-kernel - Re: linux.git: printk() problem

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: <CA+55aFyeAyOQiJFGNxiM8u+5T-8DnzRv4K8CkBxAZBij0mLpEA@mail.gmail.com>
Date:   Sun, 23 Oct 2016 14:13:29 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Joe Perches <joe@...ches.com>
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Petr Mladek <pmladek@...e.cz>
Subject: Re: linux.git: printk() problem

On Sun, Oct 23, 2016 at 1:33 PM, Joe Perches <joe@...ches.com> wrote:
>
> Perhaps it could be a pool of active thread
> continuation buffers.

Yes, we could probably do with just a couple of entries. Even just two
would probably catch almost all cases.

That said, having dealt with that code, I'd hate to make it more
complex again for something where the preferred solution is "don't do
it".

             Linus