Ghostboard pixel Skip to content

A Problem in the Linux Kernel Yet Again: This Time, It's Bcachefs!

Some issues with the developer of bcachefs in the Linux Kernel community. Maybe, it's just being overblown? What do you think?

2024's been an interesting year for the Linux kernel, more so in the final months when we saw the expulsion of Russian maintainers over compliance requirements, and then a subsequent move by Russia to build its own Linux community.

Linux kernel development is no stranger to a few controversies here and there, but geopolitics affecting their work was a surprise indeed.

Unfortunately, something else has happened now that involves Bcachefs, the copy-on-write (COW) filesystem for Linux that focuses on reliability and being a robust alternative to ZFS and Btrfs.

What's Going On With Bcachefs?

a screenshot of a blog titled trouble in the kernel by kent overstreet
Source: Kent Overstreet

Kent Overstreet, the creator of Bcachefs, has put out a blog detailing how the future of Bcachefs in the Linux kernel looks uncertain, as Linus Torvalds has rejected a pull from him for the upcoming Linux 6.13, citing “an open issue with the CoC board”.

If you didn't know, the Linux kernel CoC committee (mentioned as “board” above) is tasked with enforcing the Code of Conduct (CoC) that applies to the project, both in project spaces and in the public. The latter is applicable when an individual is publicly representing the project or the community as a whole, including on social media or online/offline events.

The consensus is that a recent offensive reply (back in September) by Kent to Linux memory management (MM) developer, Michal Hocko is behind the suspension. As you can see below, Kent was not happy with how Michal was handling things related to PF_MEMALLOC_NORECLAIM.

In subsequent replies, Kent was asked by Shuah Khan of the Linux kernel CoC committee to not use such language, and to adhere to the Code of Conduct. To that, Kent responded that he had worked this out with Michal privately, with the CoC committee receiving the copies of the interactions.

However, Shuah didn't let it go, asserting that he had to apologize. Consequently, there has been plenty of discussion over this, with Kent refusing to apologize publicly.

What Happens Now?

a screenshot of the formalized coc enforcement policy for linux kernel being announced on lore.kernel.org

All of this seems to have been taken up a notch by the formalized CoC enforcement policy that was published on November 14, 2024. It expands on what kind of actions might be taken in cases of unacceptable behavior.

There are provisions on it that can be used against offenders. With a public apology by the offender being the first one. If an offender doesn't do that, then a ban from participating in kernel development, either for a short period or a full kernel development cycle, could be handed out.

In such a case, the offender may be required to publicly apologize to get back in, but that is not a mandatory requirement. The CoC committee has the final say in that.

Kent's blog appeared a few days after the publishing of the policy, so it looks like this is likely to be a drawn-out dispute. In the blog, he goes on to share that his reply was not meant to be malicious or personal, and things like this happen when developers get into technical arguments.

As for the CoC's handling of the situation (via Shuah), many Linux kernel maintainers, including Kent, are unhappy with how heavy-handed the interactions have been, with CoC enforcement also being brought into question.

If you are interested in reading the ongoing conversation surrounding this, then you can go through the original thread that is at the core of it all.

In the end, some questions remain: What will happen to the Bcachefs implementation in the mainline Linux kernel? Will it stay or go away? Is this a temporary suspension for Kent Overstreet, or a more permanent one?

For answers to all that, we have to wait and see what happens.

💬 Tell me what you think of this situation in the comments below!

Suggested Read 📖

No Russians in my Kernel! Geopolitics Reaches Linux Project
So, geopolitics into the mix, and it is a US-thing, or not?

Here's why you should opt for It's FOSS Plus Membership

  • Even the biggest players in the Linux world don't care about desktop Linux users. We do.
  • We don't put content behind paywall. Your support keeps it open for everyone. Think of it like 'pay it forward'.
  • Don't like ads? With the Plus membership, you get an ad-free reading experience.
  • When millions of AI-generated content is being published daily, you read and learn from real human Linux users.
  • It costs just $2 a month, less than the cost of your favorite burger.

Latest