linux-kernel - RE: [GIT PULL] printk for 5.20

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: <45448fe59f7242fd90c5271a72ca937c@AcuMS.aculab.com>
Date:   Wed, 3 Aug 2022 14:46:08 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Sebastian Andrzej Siewior' <bigeasy@...utronix.de>,
        Linus Torvalds <torvalds@...ux-foundation.org>
CC:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <senozhatsky@...omium.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        John Ogness <john.ogness@...utronix.de>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Rasmus Villemoes <linux@...musvillemoes.dk>,
        Thomas Gleixner <tglx@...utronix.de>, Jan Kara <jack@...e.cz>,
        Peter Zijlstra <peterz@...radead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [GIT PULL] printk for 5.20

> On 2022-08-02 20:19:34 [-0700], Linus Torvalds wrote:
> > Seriously, even if you have strict RT requirements, you may also have
> > strict debugging requirements, and if something goes wrong, you want
> > to KNOW ABOUT IT. At that point, your RT rules may well fly out the
> > window, because you have more serious problems.
> >
> > End result: no way will I accept this kind of completely arbitrary and
> > frankly not very intelligent patch.
> >
> > If people want to disable console printing, that's THEIR CHOICE. It
> > could be a new config variable where you ASK people about what they
> > want. Not this kind of idiotic tying together of things.

There is already the sysctl kernel.printk
That can be used to limit the effects of console logging.

I don't actually remember the 'threaded console' stuff being
enabled/disabled in much the same way.

I end up setting '6 4 1 7' to avoid serial port delays.
But (in some sense) it might be useful to have the supressed
'info' messages output by a thread.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)