linux-kernel - Re: [GIT PULL] tracing: user

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]

Message-ID: <20230624135056.263e0ba9@rorschach.local.home>
Date:   Sat, 24 Jun 2023 13:50:55 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Beau Belgrave <beaub@...ux.microsoft.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        sunliming <sunliming@...inos.cn>
Subject: Re: [GIT PULL] tracing: user_event fix for 6.4


Linus,

On Fri, 23 Jun 2023 22:09:59 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> The code that does the write is basically something being monitored by
> something else that will tell it to start writing. But that something
> else could have the buffer disabled for writes. The use case for this
> is to disable the buffer, enable all the trace events you care about,
> and then enabled the buffer which is the same as enabling all events at
> the same time to get a more coherent trace.

Are you fine with the above explanation? The thing is, writes that are
dropped due to the buffer being disabled shouldn't be a concern of the
producer. It's the consumer that controls that. This is the same
behavior that is used by internal kernel trace events, and we wanted to
keep it consistent.

Would you like me to resend the pull request with an updated change log?

-- Steve