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  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:   Wed, 30 Aug 2017 11:25:28 +0900
From:   Sergey Senozhatsky <>
To:     Joe Perches <>
Cc:     Steven Rostedt <>,
        Sergey Senozhatsky <>,
        Linus Torvalds <>,
        Pavel Machek <>,
        Sergey Senozhatsky <>,
        Petr Mladek <>, Jan Kara <>,
        Andrew Morton <>,
        Jiri Slaby <>, Andreas Mohr <>,
        Tetsuo Handa <>,
        Linux Kernel Mailing List <>
Subject: Re: printk: what is going on with additional newlines?

On (08/29/17 18:52), Joe Perches wrote:
> > We could simply add a seq_buf_printk() that is implemented in the printk
> > proper, to parse the seq_buf buffer properly, and add the timestamps and
> > such.
> No need.  printk would already add timestamps.

the idea is not to do printk() on that seq buffer at all, but to
log_store(), atomically, seq buffer messages

	while (offset < seq_buffer->len) {
		log_store(seq->buffer + offset);


Powered by blists - more mailing lists