Linus Torvalds has joined the discussion regarding the resistance of the mayor to introduce Rust into the kernel. He explained that no one is forcing maintainers to learn or use the Rust language, write Rust code, or consider the presence of Rust code in the kernel. Maintainers can continue working solely with code in C and not interact with Rust. However, this does not mean they can influence the development of Rust code within the kernel, such as its integration with existing code.
Maintainers interested in advancing Rust can choose to get involved in its development and have a say in how Rust code is structured and integrated. Those who prefer not to work with Rust do not have to worry about it but also cannot influence its development.
Essentially, a protective barrier is formed around developers who only use the C language, shielding them from any issues related to Rust. This barrier works both ways, so developers who do not wish to engage with Rust cannot impact its progress. The idea is that not every maintainer can veto any Rust code, as cooperation and consideration for Rust integration is expected from some maintainers.
Regarding the controversy surrounding Rust components above the DMA subsystem, bypassing maintainers who attempted to block such additions, Linus criticized Christoph Hellwig. Linus argued that Christoph overstepped his authority by trying to control code that did not pertain to the DMA subsystem, was implemented separately, and did not fall under Christoph’s responsibility. Linus likened Christoph’s actions to trying to ban a certain driver from using DMA simply because he did not approve of it.
In conclusion, while maintainers are accountable for their code, they are not responsible for how others utilize the results of their code.