“no features in RCs” is a very basic rule, this was a forgone conclusion. If these features were so integral to data integrity, he should have kept bcachefs out of the kernel until they were ready.
post
My uneducated kernel take. Flexibility is acceptable and desirable in small projects or low impact projects.
When the majority of the internet and a good chunk of PC are dependent on your project, predictability and stability is much more important than flexibility.
Reading all the comments (between Kent and Linux), the problem is that the bcachefs dev thinks that his project (the filesystem) is the critically important one and that the Linux kernel needs to bend to his will.
I am a bcachefs user but it is pretty damn obvious to me that the production Linux kernel is more important than an experimental filesystem.
Took me way too long to figure out this stuff is called B Cache FS and not BCA Chefs.
Anyone else here actively put off by Linux drama and headlines like "Torvalds Drops support After Clash!"
EDIT: New rule?
I'm really glad Torvalds is the kind of person to flip articles like this off and carry on with his day and just not be affected by it at all. When the time comes, I hope whoever carries the torch is just as well.
That's a good point, I have no doubt Linux would not be in the position it is if he were more sensitive to it.
At the very least, it would be far more of a circus, as the follow-up articles would read "LINUX KERNEL CREATOR LINUS TORVALDS MAKES DEVESTATING REPLY TO FOSS DRAMA!"
But yeah, I think shit like that would just make devs want to go work for a company, because at least when they make a shitty closed sourced, exploitive program people are mad at the company, not them, specifically. They don't have to deal with this shit.
This is a non-issue, being over-reported by people looking for clicks. A minor technical matter being handled by the person ultimately responsible for handling such things
Yeah for sure there's ton of clickbait, but this isn't "a minor technical matter". The news here isn't the clash over whether the patch should be accepted in the RC branch, but the fact that Linus said he wants to remove bcachefs from the kernel tree.
An experimental capability being kicked out of the kernel, so that it has to settle for being a kernel module or custom forks of the kernel, is absolutely a minor matter
Filesystems are incredibly antiquated, and while I don't agree with Kent's attitude, it is very important in the long run that filesystems catch back up.
As it stands just about any enterprise system you can poke a stick at is rolling their own customised file storage system, with a traditional filesystem typically being a misshapen dead weight sitting somewhere in the middle of it - existing because it's the only thing the kernel can integrate with.
It is pretty important that this trend reverses, and bcachefs was a big step in the right direction. Unfortunate that Kent is the way he is.
I don't see any drama. It's just people working together, having different priorities yet still getting things done. Some friction is to be expected.
Put off in what way?
Please don't sealion me.
Don't you dare turn this around on me.
Ah, sorry to read - I like the idea of Bcachefs and would have been happy to have it ready for production eventually.
OTOH it seems the recent years I read more about the drama about Bcachefs commits to the kernel, than about any technical parts of Bcachefs.
Can't wait for a new Brodie-video on this topic. Stay tuned for some comments.
Good I didn't choose bcachefs
It's an interesting filesystem, but you shouldn't use it at this point unless you know what the hell you're doing. You'll need to be able to notice, report and help resolve bugs, and under no circumstances use it for production or where you can't afford to lose some or all of the data on the partition.
This is actually kind of tame by Kent's standards.
It's a shame honestly. He seems smart but he doesn't seem to realize that the linux kernel is not just for his "customers." It's literally for everyone. He seems to think he can make whatever changes and it'll be fine (perhaps it will be) but doesn't understand that the people using bcachefs are a tiny, tiny, tiny portion of overall Linux users who need stability in the kernel.
That and anyone using bcachefs 1) probably shouldn't be holding so much data on it given how it changes and 2) should be able to build a kernel with the patches if needed because it's experimental and...if you're doing that you should know what you're doing.
Kent's acting like this is a production filesystem and users need to have his fixes RFN. Anyone using bcachefs in anger needs their head examined. They should expect it to blow up completely, and they can pick up the pieces.
As expected. I like bcachefs and the features it already has, but switched away because of the drama/instability.
all 37 comments