{"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\/hu\/blog\/news\/linus-torvalds-nameren-vklyuchat-svyazannye-s-rust-izmeneniya-v-obhod-mejntejnerov","title":{"rendered":"Linus Torvalds a Rusthoz kapcsol\u00f3d\u00f3 v\u00e1ltoztat\u00e1sokat tervezi a karbantart\u00f3k megker\u00fcl\u00e9s\u00e9vel bevezetni","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Christoph Hellwig, a maintainer of the DMA, KVM, Slab Allocator subsystems, and PowerPC architecture in the Linux kernel, has fundamentally refused to accept Rust bindings for the DMA subsystem into the kernel. He joined the discussion on the Rust support rules 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 independent decisions about including Rust-related code in their subsystems. Christoph claims that Linus Torvalds stated in a private conversation that he is firmly determined to accept Rust code into the kernel, despite maintainers' objections. Thus, developers and kernel maintainers will now have to deal with Rust, whether they want to or not. <\/p>\n
Christoph again compared the spread of Rust bindings to a cancerous tumor that will spread to all kernel subsystems and lead to fragmentation. From a unified whole, the kernel is turning into a project written in several languages, with no clear definition of when to use which language. According to Christoph, working with such a mixed codebase has become his worst nightmare, as code is constantly rewritten from one language to another and then back again under such conditions. <\/p>\n
At the same time, Christoph asks to clarify the purpose of introducing Rust into the kernel. If the goal is to solve security issues arising from low-level memory work, then modernization of the existing code is primarily required. Given that maintainers react painfully even to trivial matters, such as checks for integer overflow, it is 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 strictly to enforcement. If the goal is to simplify driver development, then the introduction of support for yet another language will only add more work and increase the burden on the already overloaded individuals maintaining the kernel's infrastructure. <\/p>\n
A Rust integr\u00e1ci\u00f3j\u00e1nak h\u00edvei a k\u00f6vetkez\u0151 c\u00e9lokat emelik ki: <\/p>\n
\n
Az \u00faj k\u00f3d Rust nyelven t\u00f6rt\u00e9n\u0151 \u00edr\u00e1sa cs\u00f6kkenti a mem\u00f3riahaszn\u00e1lat sor\u00e1n fell\u00e9p\u0151 hib\u00e1k \u00e9s versenyhelyzetek kock\u00e1zat\u00e1t, valamint kiz\u00e1rja egyes logikai hib\u00e1kat.\n
A karbantart\u00f3knak k\u00f6nnyebb lesz fel\u00fclvizsg\u00e1lni a v\u00e1ltoztat\u00e1sokat \u00e9s refaktor\u00e1lni a modulokat a Rust nyelv \u00e1ltal ny\u00fajtott garanci\u00e1k figyelembev\u00e9tel\u00e9vel.\n
A Rust nyelv fejlett lehet\u0151s\u00e9geit kihaszn\u00e1l\u00f3 absztrakci\u00f3k egyszer\u0171s\u00edteni fogj\u00e1k az \u00faj driverek \u00e9s modulok l\u00e9trehoz\u00e1s\u00e1t.\n
A modern nyelv t\u00e1mogat\u00e1sa \u00faj r\u00e9sztvev\u0151ket vonz a kernel fejleszt\u00e9s\u00e9hez.\n
A Rust eszk\u00f6zeinek alkalmaz\u00e1sa egyszer\u0171s\u00edti a k\u00f3d dokument\u00e1l\u00e1s\u00e1nak k\u00f6vetelm\u00e9nyeit. P\u00e9ld\u00e1ul a Rust for Linux projektben k\u00f6telez\u0151v\u00e9 v\u00e1lt a nyilv\u00e1nos API-k, biztons\u00e1gi k\u00f6vetelm\u00e9nyek, unsafe blokkok \u00e9s t\u00edpus invari\u00e1nsok dokument\u00e1l\u00e1sa. <\/ul>\n