I will show you mine if you show me yours.

Not that number of commits has anything to do with calling out brigading which you still seem to be committed to.

Oh I expect absolute crickets from all the people who waded into this trashing Hellwig.

Opposition to it is reactionary, not well-grounded in technical merits; most of Linux is not well-proven to be correct, only believed to be correct under typical operating conditions as estimated by several dozen experienced programmers

Try expanding that to ‘overwhelmingly correct as assessed by hundreds of thousands of programmers on tens of millions of systems globally under diverse conditions at a low end ballpark.’

Martin is not a maintainer of the Kernel/DMA which is why Hellwig clearly states he doesn’t want to add another maintainer when rejecting Martin’s offer to be a maintainer of this proposed code.

This is very clear if you read the email. If you don’t like the formatting go read the full email chain yourself, you will know where to find it if you’re so familiar with ‘kernel social dynamics’.

So you think Hellwig doesn’t understand what is and isn’t intended to go into the kernel/dma that dma maintainers would then be responsible for?

You don’t seem to be familiar with either the full conversation the developers had (its all available) or you don’t understand how the Linux project is structured and maintained.

From the email chain:

On Thu, Jan 16, 2025 at 02:17:24PM +0100, Danilo Krummrich wrote:

Since there hasn’t been a reply so far, I assume that we’re good with maintaining the DMA Rust abstractions separately.

No, I’m not. This was an explicit:

Nacked-by: Christoph Hellwig

And I also do not want another maintainer. If you want to make Linux impossible to maintain due to a cross-language codebase do that in your driver so that you have to do it instead of spreading this cancer to core subsystems. (where this cancer explicitly is a cross-languagecodebase and not rust itself, just to escape the flameware brigade).

Hellwig has some excellent points and people are up in arms solely because he’s not giving the green light for the shiny new toy.

Keep the wrappers in your code instead of making life painful for others

This is a perfectly valid approach, anyone claiming he’s resistant for no reason has never tried maintaining a multi language code base.

If you want to use something that’s not C, be that assembly or Rust, you write to C interfaces and deal with the impedance mismatch yourself as far as I’m concerned.

Again an entirely reasonable approach. There is precedence for this approach in the kernel/dma and I see no reason to change this now, unless a full kernel/dma rewrite to Rust were to occur.

Leith is telling furphies.

Where did China import that coal from? Australia. (Not only Australia but that’s not the point)

Australia isn’t doing its part, new coal mines were approved last year and exports are at an all time high.

Australians are, per capita, some of the worst GHG emitters on the planet.

Try leaving a technically correct comment first.

Like I said, people doing self hosting, they often open up ports for those services and management ports.

Some routers have backdoors built in, such as the Fortinet NGFW backdoor, that can also be exploited.

I work in this industry and believe me the risk is real, no vpns aren’t a silver bullet, but there are a few good providers out there that can help mitigate some risks of using P2P for more than piracy.

That depends on whether they are port blocking as I said.

If there was a vulnerability it would be exploited in the matter of a few minutes.

Around 10 minutes for an unpatched XP box with no firewall.

Much longer for obscure vulnerabilities in routers or more difficult to exploit vulns in hosted software.

It is also possible for vulnerabilities in peertube itself to exist, which will be an issue regardless of VPN use.

I could scan your network for vulnerabilities.

I could anyway but knowing a target used a service like peertube increases the odds of unpatched hardware or self hosted services in my experience.

If you’re using an older router you probably have a problem due to unpatched vulnerabilities.

If you self host you might have a problem, as many package maintainers and developers lag a bit behind security patches.

A good VPN provider will also block unusual ports.