Hacker News Reader

That doesn't really seem to map onto the situation since Greg himself released a 6.12 with the patch earlier today.

I don't know what you mean at all. I'm just repeating known kernel policy here. What does 6.12 have to do with anything?

What is your interpretation of why Greg KH released a version of 6.12 with this fix in it today, other than to help distributions avoid this vulnerability?

Why would he ever... not release a new version? I don't get what you're trying to say - I'm stating Greg's explicit policy on the topic. If he did something outside of that policy, that wouldn't change anything.

If he doesn't believe in the "concept of vulnerabilities" then it is remarkable that he released a 6.12 targeted on this one fix. Why would he do that otherwise?

Sorry but he literally doesn't and nothing you say is going to change that he has explicitly stated that. This isn't up for debate, go ask him yourself, literally go to the first blog post on his site.

As for the latest patch, Greg is currently being forced to clean up a big fucking mess by external parties. And he's miserable about it.

Reply on news.ycombinator.com