Bug ID | 1109665 |
---|---|
Summary | Disabling f2fs |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.3 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Kernel |
Assignee | kernel-maintainers@forge.provo.novell.com |
Reporter | nborisov@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
This issue is to be used as a collection of all discussions regarding disabling the compilation of f2fs in various opensuse distributions. Currently this filesystem received only sporadic CVE-related backports. In the process of doing said backports I have also identified several drawbacks which make it rather hard to support and provide sensible experience: 1. There are a bunch of validation checks which are not being backported since they are not linked to a particular CVE as such the stability of the filesystem is questionable even with CVE backports. 2. Currently the filesystem doesn't have a way to disable mounting of filesystems created with newer kernels, containing on-disk incompatible changes. I have talked with one of the maintainers and they recognize this fact but so far no one is working on this. This is a pretty major since newer images could potentially crash older kernels not being able to properly parse them. 3. All in all this leads me to believe that f2fs requires a rather controller environment in terms of kernel/tools versions so is not a good candidate to be included in a community-based distribution kernel. I've already spoken to release manager for leap/tumbleweed and they are fine with disabling it.