linux-kernel - Re: [PATCH v4 00/34] Printbufs - new data structure for building strings

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 19 Jul 2022 21:31:49 -0400
From:   Kent Overstreet <kent.overstreet@...il.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     linux-kernel@...r.kernel.org, linux-mm@...ck.org, pmladek@...e.com,
        enozhatsky@...omium.org, linux@...musvillemoes.dk,
        willy@...radead.org
Subject: Re: [PATCH v4 00/34] Printbufs - new data structure for building
 strings

On 7/19/22 21:11, Steven Rostedt wrote:
> On Tue, 19 Jul 2022 20:17:45 -0400
> Kent Overstreet <kent.overstreet@...il.com> wrote:
> 
>>> More specific please.
>>
>> Steve, look at the man page for snprintf if you don't see what I mean.
>> This discussion has become entirely too tedious, and your _only_
>> contribution to the discussion on pretty-printers has been "why isn't
>> this using this thing I made?".
> 
> No, my response is, why should we replace something that is working
> just fine?
For you. For your code.

Look, Steve, I've tried to work with you. And I've given you reasons why 
seq_buf doesn't work for vsprintf.c, and more general cases. You have 
not responded _at all_ with technical reasons or discussion, all you've 
done from the very start is lecture me on process.

And, to be blunt, the time to have the printbuf vs. seq_buf discussion 
was months ago. I tried to start that discussion with you, and you 
ghosted on IRC when I started talking about the things in seq_buf that 
would have to change.

Like I said, I'll CC you when v5 is posted.