linux-kernel - Re: [GIT PULL] bcachefs changes for 6.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1935642.tdWV9SEqCh@lichtvoll.de>
Date: Sun, 10 Aug 2025 10:02:46 +0200
From: Martin Steigerwald <martin@...htvoll.de>
To: Theodore Ts'o <tytso@....edu>, Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Josef Bacik <josef@...icpanda.com>, Aquinas Admin <admin@...inas.su>,
 Malte Schröder <malte.schroeder@...ip.de>,
 Linus Torvalds <torvalds@...ux-foundation.org>,
 "Carl E. Thompson" <list-bcachefs@...lthompson.net>,
 linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17

Hi Kent, hi,

Kent Overstreet - 10.08.25, 05:17:44 CEST:
> I think you guys have been taking this a bit too far.

I am not sure who is right here. Or right to what extend.

And maybe that is not even the question.

But Kent, if your priority is the users of BCacheFS, look at the result:

The current result is a disservice to users.

Maybe even a huge one.

And likely a disservice to developers as well.

Is this result really what you like to achieve?

Cause if not, I can assure you that by doing the same thing over and over 
and over again you will yield exactly the same result over and over and 
over again. Just look at the past: This has been going in *predictable* 
cycles.

If you go on to do the same thing over and over again that drives off 
people, then that is exactly the result you will be receiving.

So if you do not adapt your behavior and do something *different* next 
time… *whether you like it or not* (!) you need to wait until someone else 
does. And that "until" may never happen. You can only influence what you 
do. So do you like to continue to give the power to change something in 
here to someone else by blaming everyone but you? That would be a lot of 
wasted energy.

You are not going to change the dynamics of power within the kernel 
development community by what you have been doing all the time.

Of course this goes the other way around as well: As long as people try to 
change each other in here, this is not going anywhere. The only change you 
can affect is a change within yourself.

So maybe take a while off mail, breathe deeply and meditate or do whatever 
helps you to see what within you contributes to the result we see here. I 
will do the same.

All in all again I point out: This cannot by solved by writing mails. You 
need to *speak* to each other.

Enough already.

Best,
-- 
Martin