linux-kernel - Re: smpboot: CPU numbers printed as warning

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]

Date:   Tue, 16 Feb 2021 12:17:24 +0106
From:   John Ogness <john.ogness@...utronix.de>
To:     Borislav Petkov <bp@...en8.de>, Petr Mladek <pmladek@...e.com>
Cc:     Paul Menzel <pmenzel@...gen.mpg.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
        LKML <linux-kernel@...r.kernel.org>, it+linux-x86@...gen.mpg.de,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Subject: Re: smpboot: CPU numbers printed as warning

On 2021-02-16, Borislav Petkov <bp@...en8.de> wrote:
>> Also you should add '\n' into the previous string to make the behavior
>> clear. It will always be printed on a new line when pr_info()
>> is used.
>
> This was made to use pr_cont() on purpose so that the output is
> compact,

It is supported to provide loglevels for CONT messages. The loglevel is
then only used if the append fails:

    pr_cont(KERN_INFO "message part");

I don't know if we want to go down that path. But it is supported.

John Ogness