© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
5466644
demo site
(Get the code!)
Hi, patch author here. You can ask BTRFS maintainers by mailing to the <email address hidden> mailing list. Also, the patch author email address is in the commit itself, for quick questions. :-)
I just stumbled across this ubuntu issue while being bored and reading https:/
If you're using btrfs, I would personally not recommend using a linux 4.4 kernel, but at least 4.9 and preferably 4.14. The btrfs project does not really have enough resources to properly manage tracking and sorting out fixes and updating older kernels than the latest LTS. The latest LTS (4.14 now) has the highest chance of getting important fixes, for all other versions it depends on the knowledge and decisions of the patch author what happens. (By the way, this is also the reason Redhat dropped btrfs support: if you don't really know what you're doing (which means investing in having a bunch of serious btrfs developers in your team) then trying to selectively backports things becomes a real mine field quickly.)
Aside from that, the "has a negative impact on usability" is certainly true, and including this change in kernels < 4.14 that are used by Joe Average who wants to use btrfs is certainly useful.
Backporting this one is not risky, the change doesn't bite much. Apart from the mount option behaviour change that's mentioned (which can either be picked or ignored) the old code has pretty much been there since 2008.
Disclaimer: I'm a Debian user, so I don't follow ubuntu kernels closely.
When looking at...
https:/
...I would recommend btrfs users to just move to Ubuntu 18.x.