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:   Tue, 29 Aug 2017 16:59:24 -0700
From:   Linus Torvalds <>
To:     Steven Rostedt <>
Cc:     Sergey Senozhatsky <>,
        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 Tue, Aug 29, 2017 at 4:50 PM, Steven Rostedt <> wrote:
> What about using the seq_buf*() then?

They do have the nice property that because we use them for various
/proc files, there are some helper functions in addition to just the

Ie seq_buf_putmem_hex().

And yeah, you can just do

        char buffer[80];
        struct seq_buf s;

        seq_buf_init(&s, buffer, sizeof(buffer));

if you want to use a stack buffer for a single line.


Powered by blists - more mailing lists