linux-kernel - Re: [RFC] LTTng upstreaming next steps

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: <CAHk-=wiT9Cz+EbbuKozqiu7DnZQ7ftAWSmGf-xy_CdhJPCsNSg@mail.gmail.com>
Date: Mon, 14 Jul 2025 13:00:27 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Steven Rostedt <rostedt@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	Christoph Hellwig <hch@...radead.org>, "Masami Hiramatsu (Google)" <mhiramat@...nel.org>, 
	Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>, 
	Thomas Gleixner <tglx@...utronix.de>, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] LTTng upstreaming next steps

On Mon, 14 Jul 2025 at 12:41, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com> wrote>
> A) Bulk upstreaming

Honestly, I don't see the point.

The reason the current tracting infrastructure got merged was that
people were willing to do it incrementally.

I was hoping that there would be some kind of eventual merging of the
different ring buffers etc. That was discussed as a hopeful end goal
originally, but here were are, decades later, and it never happened.

And honestly, I am NOT interested in just having two different tracing models.

If people need two tracing models, then the other one will be out of
tree. It's that simple.

Because if people haven't been able to agree on common models in the
decades past, I really don't see the point in maintaining two models
indefinitely side-by-side in the upstream kernel.

So as far as I'm concerned, this discussion is not a discussion.
Either there's a way to merge things incrementally with SHARED
infrastructure, or there isn't.

No "two different and disjoint trace buffers".

No "two different and disjoint trace interfaces".

And very clearly - based on history - that unification will never happen.

            Linus