linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Carl E. Thompson" <list-bcachefs@carlthompson.net>
To: "Malte Schröder" <malte.schroeder@tnxip.de>,
	"Kent Overstreet" <kent.overstreet@linux.dev>,
	"Konstantin Shelekhin" <k.shelekhin@ftml.net>
Cc: admin@aquinas.su, linux-bcachefs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17
Date: Mon, 11 Aug 2025 17:44:03 -0700 (PDT)	[thread overview]
Message-ID: <145928469.642.1754959443409@mail.carlthompson.net> (raw)
In-Reply-To: <28dbd3e0-8d5b-4dfe-a7e7-3a73347480f6@tnxip.de>


> On 2025-08-11 11:40 AM PDT Malte Schröder <malte.schroeder@tnxip.de> wrote:
> ...

> Frankly for me as a user who does probably not know the hole picture you
> seem to just be spewing paranoid hate into these threads which I do not
> quite understand.

I apologize for coming across that way. I guess I'm just very frustrated at this whole situation and the fact that it appears from my perspective to be damaging the reputation and credibility of Linux which is something I care about very deeply.

And I'm angry. I'm angry because of the damage to Linux and because Kent appears to be misrepresenting events in a way that make others whom I respect look bad. For example, here in this thread a key point Kent is claiming is that no one has ever told him specifically anything that he's done wrong and essentially that other kernel developers are attacking him for no good reason. That's simply not true. Linus has explained his mistakes to Kent on multiple occasions. Other kernel developers have tried to help him see what he's doing wrong. Random users (including I) have tried to help him interact better with others. It is simply not true that no one has told him what he's done wrong.

There are many other things about Kent's recounting of events and things he has said in this thread that also seem to be objectively not true. If anyone thinks it would be useful I can itemize those things I've noticed.

I'm also angry because I'm a long-time bcachefs supporter. I started using bcachefs years ago long before it was in the kernel. I've put a lot of my own work into running it, testing it and submitting bug reports. Up until a few months ago I had about 20 bcachefs filesystems of varying sizes spread across my personal workstations, servers and lab. I even integrated bcachefs as a core part of a relatively large (by my standards) project I'm hoping to release some time before the end of the year. There were some warning signs along the way but I ignored them because I really, really wanted bcachefs. 

But eventually I had to ask myself... If Kent repeatedly brings conflict and discord to a group that needs to work closely and trust each other, and if Kent repeatedly makes the same interpersonal mistakes and doesn't learn from them, and if Kent seemingly regularly misrepresents things... Can I really trust him or his code? My personal answer to that is "no." So I've migrated everything I have from bcachefs and I'm angry about wasting all the time and effort I put into it.

Finally I'm angry because so many people appear to be thinking only of themselves. They appear to think: *I* really want to use bcachefs and it would be much more convenient for *me* if it were in the kernel therefore it should be in the kernel and the other kernel developers should let Kent do whatever he wants no matter how it makes them feel about their work environment.

My opinion is that's a really great recipe for making Linux worse: Suck the joy out of the other kernel developers' jobs by forcing them to work with someone who seemingly doesn't respect anyone but himself simply because *we* (the users) really want bcachefs. Go that route and valuable contributors will mentally check out or worse leave altogether. It will spread like cancer (and probably already is). It's an absolute fact that people who are unhappy in the workplace do worse work. Let's keep the kernel developers happy.

Again, I apologize for being overly harsh.

Carl

PS: I do hope that Kent can work things out and figure out how to contribute in a way that's useful for others and makes him happy. But we sometimes have to weigh giving someone like Kent another chance against the harm keeping him around does to other people we care about.

  reply	other threads:[~2025-08-12  0:44 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 15:14 [GIT PULL] bcachefs changes for 6.17 Kent Overstreet
2025-08-05 21:19 ` Malte Schröder
2025-08-05 22:41   ` Carl E. Thompson
2025-08-07 12:42     ` Aquinas Admin
2025-08-09 17:36       ` Kent Overstreet
2025-08-09 19:21         ` Josef Bacik
2025-08-09 20:37           ` Kent Overstreet
2025-08-09 21:34             ` Kent Overstreet
2025-08-10  2:24             ` Theodore Ts'o
2025-08-10  3:17               ` Kent Overstreet
2025-08-10  4:05                 ` Sasha Levin
2025-08-10  4:13                   ` Kent Overstreet
2025-08-10  4:26                     ` Gerald B. Cox
2025-08-10  5:17                       ` Kent Overstreet
2025-08-10  5:59                       ` Theodore Ts'o
2025-08-10  6:51                         ` Kent Overstreet
2025-08-10 10:22                         ` Martin Steigerwald
2025-08-11 15:48                         ` Peanut gallery 2c James Lawrence
2025-08-11 16:08                           ` Kent Overstreet
2025-08-11 17:00                             ` James Lawrence
     [not found]                             ` <aJsIOj6jbPKayO0s@mayhem.fritz.box>
2025-08-12 16:26                               ` Kent Overstreet
2025-08-11 16:48                   ` [GIT PULL] bcachefs changes for 6.17 Aquinas Admin
2025-08-10  8:02                 ` Martin Steigerwald
2025-08-10  6:05               ` Carl E. Thompson
2025-08-11 16:02           ` Aquinas Admin
2025-08-11 16:09             ` Kent Overstreet
2025-08-09 23:01         ` Matthew Wilcox
2025-08-09 23:13           ` Kent Overstreet
2025-08-12  7:49             ` Jani Partanen
2025-08-12 10:09               ` Martin Steigerwald
2025-08-11  9:51         ` Konstantin Shelekhin
2025-08-11 14:26           ` Kent Overstreet
2025-08-11 18:13             ` Carl E. Thompson
2025-08-11 18:40               ` Malte Schröder
2025-08-12  0:44                 ` Carl E. Thompson [this message]
2025-08-11 18:48               ` Aquinas Admin
2025-08-11 19:42               ` Martin Steigerwald
2025-08-11 21:04             ` Konstantin Shelekhin
2025-08-12  1:08               ` Kent Overstreet
2025-08-12  6:52             ` asdx
2025-08-12  7:04               ` Kent Overstreet
2025-08-12  7:17                 ` asdx
2025-08-12 19:35             ` Keith Busch
2025-08-12 20:03               ` Kent Overstreet
2025-08-12 20:30                 ` Keith Busch
2025-08-12 20:31                   ` Kent Overstreet
2025-08-12 20:38                     ` Keith Busch
2025-08-12 20:45                       ` Kent Overstreet
2025-08-12 20:54                         ` Keith Busch
2025-08-12 20:57                           ` Kent Overstreet
2025-08-11 16:45           ` Aquinas Admin
2025-08-10  4:29       ` Gerhard Wiesinger
2025-08-07 14:27   ` Martin Steigerwald
2025-08-07 17:29   ` Peter Schneider
2025-08-10  6:20 ` Gerhard Wiesinger
2025-08-10 10:32   ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=145928469.642.1754959443409@mail.carlthompson.net \
    --to=list-bcachefs@carlthompson.net \
    --cc=admin@aquinas.su \
    --cc=k.shelekhin@ftml.net \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malte.schroeder@tnxip.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).