Why New Linux File-Systems Face Higher Hurdles: Q&A on Kernel Guidelines

By ✦ min read

<p>As the Linux kernel continues to evolve, the sheer number of file-systems integrated into the source tree has created a growing workload for maintainers of the virtual file-system (VFS) layer. To address this, kernel developers have introduced formal documentation outlining stricter requirements for any future file-system proposals. Below, we answer common questions about this shift, the burden it addresses, and what it means for contributors seeking to add new file-systems to the mainline kernel.</p> <h2 id="q1">What is causing the burden on Linux VFS maintainers?</h2> <p>The Linux kernel currently hosts dozens of file-systems, from common ones like ext4 and XFS to niche or experimental options. Each file-system interacts with the VFS layer, and as new file-systems are added, the VFS code must accommodate their unique behaviors, caches, and locking mechanisms. Over time, this proliferation has increased the complexity of maintaining core VFS code. Minor changes to the VFS can inadvertently break obscure file-systems, requiring additional testing and compatibility fixes. Maintainers report that the time spent reviewing and patching these interactions has grown substantially, creating a bottleneck that slows down overall kernel development.</p><figure style="margin:20px 0"><img src="https://picsum.photos/seed/3237905065/800/450" alt="Why New Linux File-Systems Face Higher Hurdles: Q&amp;A on Kernel Guidelines" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px"></figcaption></figure> <h2 id="q2">What new documentation has been introduced to address this?</h2> <p>To streamline the process and reduce future maintenance overhead, kernel developers have published a set of formal guidelines. This documentation outlines clear criteria that any proposed file-system must meet before it can be considered for inclusion in the mainline kernel. The goal is to ensure that new file-systems are not only well-designed but also prepared for long-term maintenance within the kernel tree. The documentation encourages early community feedback, requires a proven implementation, and stresses the importance of comprehensive testing. It also establishes expectations for ongoing support, including bug fixes and feature updates, to prevent orphan file-systems from accumulating.</p> <h2 id="q3">What are the key requirements for a new file-system to be accepted?</h2> <p>Proposed file-systems must demonstrate <strong>robustness</strong> through thorough testing on various architectures, stability under stress, and compatibility with existing tools. The code must be modular and well-documented, with a clear separation from VFS internals. Submitters are also required to show a plan for <strong>ongoing maintenance</strong>, including a designated maintainer or team. Additionally, the file-system should address a real need not already covered by existing alternatives. Benchmarking data comparing performance and reliability against similar file-systems is often requested. Finally, integration with the kernel's build system must be clean, and any user-space utilities must be provided alongside the kernel code.</p> <h2 id="q4">How do these guidelines affect smaller contributors or experimental projects?</h2> <p>While the new requirements raise the bar, they are not meant to shut out innovation. Small contributors can still propose experimental file-systems, but they are encouraged to start as kernel modules or out-of-tree projects first. This allows the community to test and refine the code without adding immediate burden to VFS maintainers. The guidelines also suggest <em>partnering with experienced kernel developers</em> to navigate the submission process. For truly novel ideas, a proof-of-concept implementation published outside the main tree can gather feedback and prove value before a formal inclusion request. In this way, the rules aim to foster quality over quantity.</p> <h2 id="q5">What changes might users notice if this policy is enforced strictly?</h2> <p>For everyday Linux users, the most visible effect will be <strong>fewer new file-systems</strong> appearing in mainline kernels over the short term. Instead of many experimental additions, users can expect more polished and stable file-systems when they do arrive. The VFS layer should become more reliable and faster to update, resulting in fewer regressions across distributions. System administrators may also appreciate clearer documentation on supported file-systems and their maintenance status. Over the long run, the policy could encourage a more sustainable ecosystem where legacy file-systems are deprecated in favor of better-maintained alternatives.</p> <h2 id="q6">Is there a risk of stifling innovation with these stricter rules?</h2> <p>Kernel maintainers acknowledge this concern but argue that the current situation—where dozens of file-systems each require bespoke VFS adjustments—already hinders innovation by consuming upstream resources. The guidelines are designed to channel creative ideas into more structured development paths. For example, an innovative file-system can leverage existing kernel frameworks like FUSE (File-system in Userspace) to prove its concept without touching VFS internals. Once validated, it may later be considered for in-kernel inclusion under the new rules. Thus, the policy aims to balance novelty with long-term maintainability, ensuring that the kernel remains both innovative and stable.</p>