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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 20 Jun 2022 18:26:58 -0700
From:   Joe Perches <joe@...ches.com>
To:     Kent Overstreet <kent.overstreet@...il.com>
Cc:     David Laight <David.Laight@...LAB.COM>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        "pmladek@...e.com" <pmladek@...e.com>,
        "rostedt@...dmis.org" <rostedt@...dmis.org>,
        "enozhatsky@...omium.org" <enozhatsky@...omium.org>,
        "linux@...musvillemoes.dk" <linux@...musvillemoes.dk>,
        "willy@...radead.org" <willy@...radead.org>
Subject: Re: [PATCH v4 00/34] Printbufs - new data structure for building
 strings

On Mon, 2022-06-20 at 20:57 -0400, Kent Overstreet wrote:
> On Mon, Jun 20, 2022 at 05:38:51PM -0700, Joe Perches wrote:
> > On Mon, 2022-06-20 at 11:07 -0400, Kent Overstreet wrote:
> > > On Mon, Jun 20, 2022 at 04:19:31AM +0000, David Laight wrote:
> > > > I really think that is a bad idea.
> > > > printk() already uses a lot of stack, anything doing a recursive
> > > > call is just making that worse.
> > > > Especially since these calls can often be in error paths
> > > > which are not often tested and can already be on deep stacks.
> > > 
> > > We went over this before - this patch series drastically reduces stack usage of
> > > sprintf by eliminating a bunch of stack allocated buffers. Do try to keep up...
> > 
> > I generally agree with David.
> > 
> > I think Kent has not provided data that this actually _reduces_
> > stack usage.
> 
> I think the people who are comfortable with reading C can discern that when
> large stack allocated character arrays are deleted, frame size and stack usage
> go down.

I am very comfortable reading C.

You have not provided any data.