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: <20250714163755.1de132e9@gandalf.local.home>
Date: Mon, 14 Jul 2025 16:37:55 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, 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 16:27:50 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> > And very clearly - based on history - that unification will never happen.  
> 
> Unfortunately, I think you're right. :-(

Actually, let me take that back. I think you are right as long as one is
out of tree. Because there's no incentive to merge them.

If LTTng were to be in tree, it would be much easier to work on a strategy
to merge the infrastructure as the maintainers of both would have better
access to each other's code.

The Linux kernel has had a long history of two or more ways of doing
something that eventually was merged into a single shared infrastructure.

But as long as one is out of tree, it will never happen. That's because it
is much harder to merge infrastructure together when they are separated
like that.

-- Steve