linux-kernel - Re: printk: what is going on with additional newlines?

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: <1504028893.2040.32.camel@perches.com>
Date:   Tue, 29 Aug 2017 10:48:13 -0700
From:   Joe Perches <joe@...ches.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Pavel Machek <pavel@....cz>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Petr Mladek <pmladek@...e.com>,
        Steven Rostedt <rostedt@...dmis.org>, Jan Kara <jack@...e.cz>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Jiri Slaby <jslaby@...e.com>, Andreas Mohr <andi@...as.de>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: printk: what is going on with additional newlines?

On Tue, 2017-08-29 at 10:36 -0700, Linus Torvalds wrote:
> On Tue, Aug 29, 2017 at 10:33 AM, Joe Perches <joe@...ches.com> wrote:
> > 
> > Your change broke a bunch of output.
> 
> Tough. We've done that before to force people to fix their code.

No worries.
I don't mind the change at all really.

You do seem to like enhancing your reputation against
"plays well with others" kindergarten grading.

> I'm actually upset that EVEN NOW (and it's been, what, 18 months),

Odd maths.
October 2016 to August 2017 is barely half that.

> people ask for the old broken shit behavior back.

You seem to overestimate how often people test their
code against current kernels.

And look for documentation that shows this as a
requirement.

Other than your commit log entry and some LKML chatter
I believe that you'll have a hard time finding any.

$ git grep -i KERN_CONT Documentation/
$ git grep -i pr_cont Documentation/
$