{"id":122006,"date":"2025-02-19T14:22:14","date_gmt":"2025-02-19T12:22:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/linus-torvalds-nameren-vklyuchat-svyazannye-s-rust-izmeneniya-v-obhod-mejntejnerov"},"modified":"2025-02-19T14:22:14","modified_gmt":"2025-02-19T12:22:14","slug":"linus-torvalds-nameren-vklyuchat-svyazannye-s-rust-izmeneniya-v-obhod-mejntejnerov","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pl\/blog\/news\/linus-torvalds-nameren-vklyuchat-svyazannye-s-rust-izmeneniya-v-obhod-mejntejnerov","title":{"rendered":"Linus Torvalds zamierza wprowadzi\u0107 powi\u0105zane ze sk\u0142adni\u0105 Rust zmiany z pomini\u0119ciem g\u0142\u00f3wnych deweloper\u00f3w","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Christoph Hellwig, maintainer of the DMA subsystem, KVM, Slab Allocator, and PowerPC architecture in the Linux kernel, fundamentally refused to accept Rust bindings for the DMA subsystem into the kernel, has joined the discussion on the rules for supporting Rust within the kernel, published by the Rust for Linux project. According to Christoph, such rules are useless until they are agreed upon with the community and included in the kernel documentation. <\/p>\n
Christoph also pointed out that the rules contain incorrect information regarding maintainers' ability to make decisions on including Rust-related code in their subsystems. Christoph mentioned that in a private conversation, Linus Torvalds stated he is determined to accept Rust code into the kernel, despite maintainers' objections. Therefore, developers and kernel maintainers will now have to deal with Rust, whether they want to or not. <\/p>\n
Christoph also compared the spread of Rust bindings to a cancerous tumor that will spread to all subsystems of the kernel and lead to fragmentation. From a unified whole, the kernel is turning into a project written in several languages, without a clear definition of when each language should be used. Christoph stated that working with such a mixed codebase has become his worst nightmare, as it constantly involves rewriting code from one language to another and then back. <\/p>\n
In this regard, Christoph asks to clarify the purpose of introducing Rust into the kernel. If the goal is to solve safety issues arising from low-level memory operations, then the existing code needs modernization first. Given that maintainers react painfully even to trivial things like integer overflow checks, it's unclear how to bridge the gap between one part of the kernel that does not accept even simple safety rules and another part that adheres to strict rules. If the goal is to simplify driver development, then adding support for yet another language will only increase the workload and burden the already overloaded individuals maintaining the kernel infrastructure. <\/p>\n
Je\u015bli chodzi o zwolennik\u00f3w wprowadzenia Rust do j\u0105dra, wymieniaj\u0105 oni nast\u0119puj\u0105ce cele: <\/p>\n
\n
Pisanie nowego kodu w j\u0119zyku Rust zmniejszy ryzyko b\u0142\u0119d\u00f3w zwi\u0105zanych z pami\u0119ci\u0105 i stanami wy\u015bcigu, a tak\u017ce wyeliminuje niekt\u00f3re b\u0142\u0119dy logiczne.\n
Utrzymuj\u0105cym b\u0119dzie \u0142atwiej recenzowa\u0107 zmiany i przeprowadza\u0107 refaktoryzacj\u0119 modu\u0142\u00f3w, bior\u0105c pod uwag\u0119 gwarancje oferowane przez j\u0119zyk Rust.\n
Obecno\u015b\u0107 abstrakcji wykorzystuj\u0105cych zaawansowane mo\u017cliwo\u015bci j\u0119zyka Rust u\u0142atwi tworzenie nowych sterownik\u00f3w i modu\u0142\u00f3w.\n
Wsparcie nowoczesnego j\u0119zyka przyci\u0105gnie nowych uczestnik\u00f3w do rozwoju j\u0105dra.\n
Zastosowanie narz\u0119dzi Rust upro\u015bci spe\u0142nianie wymaga\u0144 dotycz\u0105cych dokumentacji kodu. Na przyk\u0142ad w projekcie Rust for Linux wprowadzono wym\u00f3g obowi\u0105zkowego dokumentowania publicznych API, wymaga\u0144 bezpiecze\u0144stwa, blok\u00f3w unsafe i inwariant\u00f3w typ\u00f3w. <\/ul>\n