Reiserfs Experiencing Turbulent Updates
When Jeff Mahoney sent in a bunch of patches for reiserfs, he assumed that the filesystem would be frozen in maintenance mode from that point on. Things turned out differently.
The end of March, SUSE developer Jeff Mahoney had sent 35 patches to the kernel and reiserfs mailing lists. Most of them found their way into openSUSE, but not yet into the kernel. With the patch series, Mahoney wanted to bring kernel 2.6.30 to the current reiserfs state of openSUSE. He ended his thread with, "Once this is applied, I expect reiserfs to be in deep maintenance-only mode."
Shortly thereafter, Linus Torvalds responded that he merged the patches into the kernel. He advised Mahoney to thoroughly double-check the results, because he didn't have any remaining reiserfs partitions. Never to miss a joke, he ended his thread with "Heh, I hadn't expected even this" in response to Mahoney's expectation that reiserfs would go into maintenance mode.
Even though Novell needed to support the filesystem for its Enterprise products a couple more years, that seemed to be the end of the story. But a few days later kernel developer Ingo Molnar chimed in on the thread reporting that Frédéric Weisbecker, in the context of the kill-the-BKL project, was still working on removing big kernel locks (BKLs) from reiserfs. Reiserfs was a filesystem that still relied heavily on BKLs and many developers had been working on removing them as of Kernel 2.6.26. Molnar had created a special "tip:kill the Big Kernel Lock (BKL)" tree for the purpose, and Weisbecker was busily rewriting the reiserfs code to eliminate BKLs from it.
Because Weisbecker's BKL patches would change reiserfs in a fundamental way, they initially sat in a special -git tree and were only to flow into the new kernel after some intensive testing, at least not until Kernel 2.6.30. But Weisbecker's patches would be a boon for many reiserfs users. Not only would the filesystem cease using BKLs, but the locks that reiserfs subsequently needed would be by superblock (by attachment point as a rule) and not across the entire filesystem. It would lead to a performance leap on systems with multiple reiserfs partitions and multicore processors, a typical scenario for reiserfs in a server environment.
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
Go-Based Botnet Attacking IoT Devices
Using an SSH credential brute-force attack, the Go-based PumaBot is exploiting IoT devices everywhere.
-
Plasma 6.5 Promises Better Memory Optimization
With the stable Plasma 6.4 on the horizon, KDE has a few new tricks up its sleeve for Plasma 6.5.
-
KaOS 2025.05 Officially Qt5 Free
If you're a fan of independent Linux distributions, the team behind KaOS is proud to announce the latest iteration that includes kernel 6.14 and KDE's Plasma 6.3.5.
-
Linux Kernel 6.15 Now Available
The latest Linux kernel is now available with several new features/improvements and the usual bug fixes.
-
Microsoft Makes Surprising WSL Announcement
In a move that might surprise some users, Microsoft has made Windows Subsystem for Linux open source.
-
Red Hat Releases RHEL 10 Early
Red Hat quietly rolled out the official release of RHEL 10.0 a bit early.
-
openSUSE Joins End of 10
openSUSE has decided to not only join the End of 10 movement but it also will no longer support the Deepin Desktop Environment.
-
New Version of Flatpak Released
Flatpak 1.16.1 is now available as the latest, stable version with various improvements.
-
IBM Announces Powerhouse Linux Server
IBM has unleashed a seriously powerful Linux server with the LinuxONE Emperor 5.
-
Plasma Ends LTS Releases
The KDE Plasma development team is doing away with the LTS releases for a good reason.