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: <10702976.nUPlyArG6x@woolf>
Date: Mon, 11 Aug 2025 23:48:51 +0700
From: Aquinas Admin <admin@...inas.su>
To: Kent Overstreet <kent.overstreet@...ux.dev>,
 Sasha Levin <sashal@...nel.org>
Cc: Theodore Ts'o <tytso@....edu>, Josef Bacik <josef@...icpanda.com>,
 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

> 
> The kernel has thrived for over 30 years not just because of technical
> excellence, but because it has (mostly) maintained a collaborative
> environment where developers can work together despite disagreements.
> That collaborative environment IS doing right by users.
> 
Come on? It's been around for 30 years because it's financially beneficial for 
some players. Should we forget about the letters and insults that flew around 
before 2018? The Code of Conduct wasn't introduced just like that. Well, 
that's just a small remark, in general. The fact is, there are no objections 
to the technical quality of Bcachefs. The objections are exclusively about 
Kent's personality and how he conducts his affairs. Maybe someone experienced 
in resolving such issues and handling personnel conflicts could suggest a 
solution? Analyze the situation and offer methods for resolution? Especially 
since the problem is far from being solely about Kent. I suggest that instead 
of threats, hasty conclusions, and quick decisions, we turn to professionals 
with the right expertise, who are surely present in the Linux Foundation. It 
will take time, but it will help everyone become better. I hope everyone 
understands that the right solution shouldn't be dictated by someone's 
feelings or grudges—regardless of who's involved.