Comments by "Mikko Rantalainen" (@MikkoRantalainen) on "Linus Torvalds Threatens To REMOVE This File System" video.

@kuhluhOG Mainline kernel is about having a stable release. If you want to develop your filesystem driver fast and stabilize it later, it doesn't belong to mainline kernel. And Overstreet keeps arguing that his method is so good and the code is close to perfect, and at the same time he argues that he cannot wait for comments to his patches because critical bugs need to be fixed ASAP. You cannot have it both ways. You cannot have both "close to perfect code" and lots of critical bugs at the same time!
27
Followed by "I have to move fast because users are complaining about critical bugs in production". So much code quality in reality.
5
I would guess Linus is trying to keep the code in kernel because that might allow somebody to step in and start to maintain the code. It seems that Overstreet needs some middleman that tests the code and only pushes forward known good versions upstream. Kind of LTS version of bcachefs. Except that the "LTS" version here is stable for at least one kernel release cycle instead of multiple years.
1
@JPs-q1o Why copy-paste this crap to every thread? If you have personal hatred against Linus, maybe reserve a time from a local psychotherapist instead. Kernel developers have been very liberal for new developers to submit code to kernel because kernel development is hard enough that you cannot be picky about the personality if the code is good. However, there's some limit about how broken personality you can have even if your code were good. And it appears that Overstreet may be over the limit even though he has been able to maintain the bcachefs for a decade. If bcachefs wants to get into mainline, there may be need for somebody else but Overstreet to do that. Maybe that person can take the latest bcachefs at the moment kernel push window closes and then only apply pure bugfixes only until the next kernel push window opens and then submit that version for the next kernel release. That way you would get full kernel release cycle worth of waiting time to see regressions fixed without any new code being introduced at the same time. That might result in good enough code quality to be included in mainline kernel. But it seems clear that Overstreet cannot follow that process.
1
I don't understand Overstreet's behavior. First he claims that his process is so perfect the his filesystem is better than btrfs. Then he says that his bugfixes are really important and are needed ASAP because customers are complaining about bugs. You cannot have it both ways at the same time. Which one is true?
1
19:05 This part alone shows it clearly that Overstreet has no clue about mainline kernel development. The single most important rule is "no never ever break any user mode program". That basically rules out any regressions. And still Overstreet tries to argue that "it's more important to move forward". See any old flame fests where Linus has totally crapped somebody. It's always because of breaking existing stuff and causing regressions. And those things happen exactly because of inadequate testing which Overstreet doesn't seem to be ready to do.
1
I think that Overstreet is given a LOT of leaway instead of just telling him to go home already and remove whole bcachefs from the mainline is beacuse he has demonstrated that he's a smart guy and gets things done. The only problem seems to be following rules. I would expect mainline kernel rules to be improved because of this case and the improved rules will probably say something clear about the rc releases. You don't push new code or features during the rc cycles. The only accepted code during the rc cycle should be about fixing specific issues caused during the push window. If that doesn't fit your needs for your "I want to move forward fast", then your code is not mature enough to be in the kernel anyway. Try to submit it again during the next push window and spend the waiting time on testing your code.
1