Re: [TECH TOPIC] Improving kernel security & integrity by generalizing ad-hoc safety mechanisms

[Greg KH <gregkh@linuxfoundation.org>]

On Tue, Sep 08, 2026 at 03:25:48PM +0300, igor.stoppa@gmail.com wrote:
> On Tue, 8 Sept 2026 at 14:54, Greg KH <gregkh@linuxfoundation.org> wrote:
> 
> > You are forgetting that "you" are "upstream".  There is no us vs. them.
> > If you want to use Linux, you are "us".  Welcome to the community :)
> 
> Decisions about what gets merged in the Linux tree are taken by those who
> are part of the hierarchy of maintainers. And, ultimately Linus.
> That was the intended meaning.

Maintainers review code, without that, this whole discussion is moot.

> > so if you have changes that you feel are required to meet your use
> > case, wonderful, that's what we all do on a daily basis.  Post them and
> > we can work through them like anything else.
> 
> While it's clear the value put on code, I have to confess that it's
> less clear to me
> where/how to initiate any discussion about the kernel development
> process itself,
> what it entails, and if/how it can be amended.

Why are you trying to change a process that works for 4000+ people and
550+ different companies every year without even a solid real proposal
that we can review?  This is baffling to me.

> I have tried to explain the constraints we have to deal with.

I did not see any concrete constraint, just vague assumptions.

Again, please show the code, without that, none of this means anything
to us, nor should you want it to (otherwise what would keep everyone out
there sending us vague proposals as to why they are different from
everyone else and slow us all down?)

> While I'm not expecting an answer, perhaps you can advise where to
> bring up this topic?
> Clearly you don't think it's suitable for ksummit ;) , but then where?

I would suggest stepping back and learning a bit more about how we do
development here.  The first step in interacting with us, is you posting
working code for your need.  That proves that this all is something that
you really have gotten working and want actual review on how to get it
merged.  Without that, there's nothing we can do here.

thanks,

greg k-h