> ## Content Index
> Fetch the complete content index at: https://itsfoss.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# A Problem in the Linux Kernel Yet Again: This Time, It's Bcachefs!
- URL: https://itsfoss.com/news/linux-kernel-bcachefs/
- Published: 2024-11-22T11:35:21.000Z
- Updated: 2024-11-22T11:35:21.000Z
- Description: Some issues with the developer of bcachefs in the Linux Kernel community. Maybe, it's just being overblown? What do you think?
- Author: Sourav Rudra
- Tags: Linux, News, #Import 2025-11-08 21:15

2024's been an interesting year for the Linux kernel, more so in the final months when we saw the [expulsion of Russian maintainers](https://itsfoss.com/russian-linux-maintainers-geopolitics/) over compliance requirements, and then a subsequent move by Russia to [build its own Linux community](https://itsfoss.com/russia-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](https://bcachefs.org/?ref=itsfoss.com), 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](https://itsfoss.com/content/images/2024/11/Bcachefs_Linux_Kernel_-fiasco_a.png)

Source: [Kent Overstreet](https://www.patreon.com/posts/116412665?ref=itsfoss.com)

Kent Overstreet, the creator of Bcachefs, has put out [a blog](https://www.patreon.com/posts/116412665?ref=itsfoss.com) 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](https://docs.kernel.org/process/code-of-conduct.html?ref=itsfoss.com) (*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](https://lore.kernel.org/all/citv2v6f33hoidq75xd2spaqxf7nl5wbmmzma4wgmrwpoqidhj@k453tmq7vdrk/?ref=itsfoss.com#:~:text=Michal%2C%20if%20you,with%20this%20shit.) (*back in September*) by Kent to Linux [memory management](https://www.kernel.org/doc/html/v5.1/admin-guide/mm/index.html?ref=itsfoss.com) (MM) developer, [Michal Hocko](https://lwn.net/Articles/684487/?ref=itsfoss.com) is behind the suspension. As you can see below, Kent was not happy with how Michal was handling things related to *PF\_MEMALLOC\_NORECLAIM*.

![](https://itsfoss.com/content/images/2024/11/Bcachefs_Linux_Kernel_-fiasco_b.png)

![](https://itsfoss.com/content/images/2024/11/Bcachefs_Linux_Kernel_-fiasco_c.png)

The offending reply by Kent Overstreet and a following post by Shuah Khan.

In subsequent replies, Kent was asked by [Shuah Khan](https://www.linkedin.com/in/shuah-khan/?ref=itsfoss.com) 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](https://lore.kernel.org/all/vvulqfvftctokjzy3ookgmx2ja73uuekvby3xcc2quvptudw7e@7qj4gyaw2zfo/t/?ref=itsfoss.com#u:~:text=I%20believe%20Michal%20and%20I%20have%20more%20or%20less%20worked%20this%20out%20privately%20%28and%0Ayou%20guys%20have%20been%20copied%20on%20that%20as%20well%29.) with Michal privately, with the CoC committee receiving the copies of the interactions.

However, Shuah [didn't let it go](https://lore.kernel.org/all/vvulqfvftctokjzy3ookgmx2ja73uuekvby3xcc2quvptudw7e@7qj4gyaw2zfo/t/?ref=itsfoss.com#u:~:text=Thank%20you%20for%20updating%20us%20on%20the%20behind%20the%20scenes%20work,discussions.%0A%0Athanks%2C%0A%2D%2D%20Shuah%20%28On%20behalf%20of%20the%20Code%20of%20Conduct%20Committee%29), 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](https://itsfoss.com/content/images/2024/11/Bcachefs_Linux_Kernel_-fiasco_d.png)

All of this seems to have been taken up a notch by the [formalized CoC enforcement policy](https://lore.kernel.org/lkml/20241114205649.44179-1-skhan@linuxfoundation.org/?ref=itsfoss.com) 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](https://lore.kernel.org/all/vvulqfvftctokjzy3ookgmx2ja73uuekvby3xcc2quvptudw7e@7qj4gyaw2zfo/t/?ref=itsfoss.com) 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 ProjectSo, geopolitics into the mix, and it is a US-thing, or not?![](https://news.itsfoss.com/content/images/size/w256h256/2022/08/android-chrome-192x192.png)It's FOSS NewsAnkush Das![](https://news.itsfoss.com/content/images/2024/10/russian-maintainers-removed-linux-kernel.png)](https://itsfoss.com/russian-linux-maintainers-geopolitics/)