linux-kernel - Re: [PATCH 1/2] tracing: show size of requested buffer

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:   Fri, 8 Oct 2021 18:13:48 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Robin H. Johnson" <robbat2@...too.org>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        linux-kernel@...r.kernel.org, mingo@...hat.com,
        rjohnson@...italocean.com,
        Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: [PATCH 1/2] tracing: show size of requested buffer

On Thu, 7 Oct 2021 17:26:04 +0000
"Robin H. Johnson" <robbat2@...too.org> wrote:

> I was trying to think further what would make sense for the constant.
> - What are the negative impacts of a too-large value?
> - Is there demand for more reconfigurability? 
> - Should PERF_MAX_TRACE_SIZE be a knob in Kconfig?

One thing you haven't discussed was, have you hit this warning, and if so,
what were you doing?

-- Steve