linux-kernel - Re: Part of Spinning up disk... ....ready logged on separate line and as warning (default level)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <dc8d2a9d-69a7-c921-a995-d216e30ca2ee@acm.org>
Date:   Mon, 6 Dec 2021 20:13:36 -0800
From:   Bart Van Assche <bvanassche@....org>
To:     Paul Menzel <pmenzel@...gen.mpg.de>,
        "James E. J. Bottomley" <jejb@...ux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        linux-scsi@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Part of Spinning up disk... ....ready logged on separate line and
 as warning (default level)

On 12/3/21 06:48, Paul Menzel wrote:
> Also, there are four dots in `....ready`, but the log timestamps only 
> differ by one seconds.
> 
>      /* Wait 1 second for next try */
>      msleep(1000);
>      printk(KERN_CONT ".");
> 
> Any idea, how that can be?

Not sure what is going on. All I know is that KERN_CONT is considered
deprecated and that it should be avoided. From commit 45c55e92fcee 
("checkpatch: warn on logging continuations"):

     pr_cont(...) and printk(KERN_CONT ...) uses should be discouraged
     as their output can be interleaved by multiple logging processes.

Thanks,

Bart.