News for hackers. Stuff that matters.
Re:Rust support in the Linux kernel by sangnoir on Thursday December 09, 2021 @12:22AM (#29494109)
> Yes, why not?

Security updates for one. People are always complaining about insecure IoT devices/routers that get conscripted into botnets. Dropping kernel support entirely compounds to manufacturer firmware negligence - meaning end users can't update to the latest Lineage/DD-WRT/OpenWRT firmware, even if they want to.

> Most software runs fine on 10 year old linux kernels.

If you had to wrangle with world of custom Android ROMs or open source router firmware - even as a user and not a developer - you know that software does not work fine on old kernels. Trying to support both old and new kernels is a royal pain, especially if you have add shims to support old kernels that lack new features.

I thank $DIETY for Linus' pragmatic approach, I trust him to balance user support against developer zealotry. I wonder how long it'll take for Linux to go to shit after he retires. Kernel notes for v42.3: dropped support for Risc-V. Remaining supported archs are x64 and ARMv21-24

Re:Rust support in the Linux kernel by Thiez on Thursday December 09, 2021 @08:59AM (#29497358)
> Security updates for one.

I thought we were talking about new drivers being developed in Rust. Your IoT security upgrade probably doesn't include a hardware upgrade, so it will not require these new drivers.

Regardless, it is the responsibility of the device manufacturer to support their old devices. It is their problem, hold them accountable.

Re:Rust support in the Linux kernel by sangnoir on Thursday December 09, 2021 @03:57PM (#29502838)
> I thought we were talking about new drivers being developed in Rust

The discussion moved to what happens to drivers that are not ported to Rust, and GP was arguing they should be abandoned/dropped - as opposed to requiring that all driver's be switched over to Rust first.

> It is their problem, hold them accountable

How can they be held accountable, pragmatically? Also, owning a CVE-riddled, insecure device is actually the user's problem. Open firmware can at least ameliorate the situation right now: where manufacturers cant be bothered to publish/upstream/update their drivers to the latest kernel API in the same language. Asking them to rewrite drivers in Rust and upstream is obviously a tall order - barring the passing of new legislation.