{"id":119617,"date":"2024-08-25T21:43:12","date_gmt":"2024-08-25T19:43:12","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/linus-torvalds-nachal-sozhalet-chto-odobril-dobavlenie-bcachefs-v-yadro-linux"},"modified":"2024-08-25T21:43:12","modified_gmt":"2024-08-25T19:43:12","slug":"linus-torvalds-nachal-sozhalet-chto-odobril-dobavlenie-bcachefs-v-yadro-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/linus-torvalds-nachal-sozhalet-chto-odobril-dobavlenie-bcachefs-v-yadro-linux","title":{"rendered":"Linus Torvalds has begun to regret approving the addition of Bcachefs to the Linux kernel.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
In discussing the latest batch of corrections proposed for inclusion in the 6.11-rc5 kernel by the author of Bcachefs, Linus Torvalds expressed his regret about having accepted the Bcachefs file system into the kernel. Torvalds' dissatisfaction stems from the fact that Kent Overstreet, the author of Bcachefs, sends overly large patches during the release candidate phase, which not only fix bugs but also continue to develop functionality. Functional changes are only permitted in the initial development stage of a new branch, while during the rc5 phase, only small, separate fixes should be accepted, ideally not exceeding 100 lines of code. <\/p>\n
The patch submitted for Bcachefs added 1,309 lines and removed 671 lines across 39 files. Besides fixing bugs, it included two significant changes: support for a new data structure to manage the list of free elements in the cache and the ability to convert hash tables for the cache. The new structure was added to eliminate unnecessary cache locks and to prevent situations that could lead to lock contention under multi-threaded loads. <\/p>\n
This is not the first instance where large fixes for Bcachefs are sent after the window for accepting changes, nor the first time that heavier functional additions are promoted instead of simple bug fixes via patch requests at the final stages of a new branch's development. Linus Torvalds responded to the submitted pull request: <\/p>\n
Enough. The last pull request was large as well. This pull request is also too extensive, addressing issues unrelated to Bcachefs, and it doesn't even remotely signify any kind of regression. At some point, 'fixing something' just turns into development, and that is exactly the moment. Nobody in their right mind uses Bcachefs and expects stability from it, so each user represents a realm of experimentation. Bcachefs patches have become a sort of 'major development during the release cycle, not before it,' to the extent that I\u2019m starting to regret adopting Bcachefs. If Bcachefs cannot work properly according to the mainstream kernel development schedule, perhaps it shouldn't be in the mainstream kernel at all. This is beyond absurd. <\/p><\/blockquote>\n
Kent Overstreet replied that Bcachefs is definitely more reliable than Btrfs and he is working to make it even more robust and dependable than XFS and EXT4, thanks to the implementation of end-to-end data integrity. Kent also emphasized that the proposed changes directly relate to improving reliability, and while failures in other kernel subsystems may result in crashes and reboots, the cost of errors in file systems is very high and can lead to undetected data corruption that may only be noticed weeks later. <\/p>\n
Torvalds countered that there are still no major Linux distributions using Bcachefs, and pointed out that the rules of kernel release development should be followed, as there is a risk of new bugs arising from such large patches containing more than 1000 lines of code. Currently, the fixes being discussed for Bcachefs have not been accepted into the Linux kernel, and the Bcachefs developer has yet to prepare an updated pull request that avoids adding new functionality and focuses solely on bug fixes. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"