linux-kernel - Re: [PATCH v2 31/32] libluo: introduce luoctl

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: <20250729183548.49d6c2dc@gandalf.local.home>
Date: Tue, 29 Jul 2025 18:35:48 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jason Gunthorpe <jgg@...dia.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, Pasha Tatashin
 <pasha.tatashin@...een.com>, pratyush@...nel.org, jasonmiu@...gle.com,
 graf@...zon.com, changyuanl@...gle.com, rppt@...nel.org,
 dmatlack@...gle.com, rientjes@...gle.com, corbet@....net,
 rdunlap@...radead.org, ilpo.jarvinen@...ux.intel.com,
 kanie@...ux.alibaba.com, ojeda@...nel.org, aliceryhl@...gle.com,
 masahiroy@...nel.org, akpm@...ux-foundation.org, tj@...nel.org,
 yoann.congal@...le.fr, mmaurer@...gle.com, roman.gushchin@...ux.dev,
 chenridong@...wei.com, axboe@...nel.dk, mark.rutland@....com,
 jannh@...gle.com, vincent.guittot@...aro.org, hannes@...xchg.org,
 dan.j.williams@...el.com, david@...hat.com, joel.granados@...nel.org,
 anna.schumaker@...cle.com, song@...nel.org, zhangguopeng@...inos.cn,
 linux@...ssschuh.net, linux-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-mm@...ck.org, gregkh@...uxfoundation.org,
 mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
 x86@...nel.org, hpa@...or.com, rafael@...nel.org, dakr@...nel.org,
 bartosz.golaszewski@...aro.org, cw00.choi@...sung.com,
 myungjoo.ham@...sung.com, yesanishhere@...il.com,
 Jonathan.Cameron@...wei.com, quic_zijuhu@...cinc.com,
 aleksander.lobakin@...el.com, ira.weiny@...el.com,
 andriy.shevchenko@...ux.intel.com, leon@...nel.org, lukas@...ner.de,
 bhelgaas@...gle.com, wagi@...nel.org, djeffery@...hat.com,
 stuart.w.hayes@...il.com, ptyadav@...zon.de, lennart@...ttering.net,
 brauner@...nel.org, linux-api@...r.kernel.org,
 linux-fsdevel@...r.kernel.org, saeedm@...dia.com, ajayachandra@...dia.com,
 parav@...dia.com, leonro@...dia.com, witu@...dia.com
Subject: Re: [PATCH v2 31/32] libluo: introduce luoctl

On Tue, 29 Jul 2025 19:21:57 -0300
Jason Gunthorpe <jgg@...dia.com> wrote:

> > As this is an evolving mechanism, having the corresponding library in
> > the kernel similar to what we do with perf and other things makes a lot
> > of sense.  
> 
> If we did this everywhere we'd have hundreds of libraries in the
> kernel tree and I would feel bad for all the distros that have to deal
> with packaging such a thing :(
> 
> It is great for development but I'm not sure mono-repo directions are
> so good for the overall ecosystem.

I have to agree here. When libtraceevent was in the kernel, it was a pain
to orchestrate releases with distros. When it was moved out of the kernel,
it made it much easier to manage.

The main issue was versioning numbers. I know the kernel versioning is
simply just "hey we added more stuff" and the numbers are meaningless.

But a library usually has a different cycle than the kernel. If it doesn't
have any changes from one kernel release to the next, the distros will make
a new version anyway, as each kernel release means a new library release.

This luoctl.c isn't even a library, as it has a "main()" and looks to me
like an application. So my question is, why is it in tools/lib?

-- Steve