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: <aJfTPliez_WkwOF3@casper.infradead.org>
Date: Sun, 10 Aug 2025 00:01:18 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: 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

On Sat, Aug 09, 2025 at 01:36:39PM -0400, Kent Overstreet wrote:
> Yes, this is accurate. I've been getting entirely too many emails from
> Linus about how pissed off everyone is, completely absent of details -
> or anything engineering related, for that matter. Lots of "you need to
> work with us better" - i.e. bend to demands - without being willing to
> put forth an argument that stands to scrutiny.

Kent, if you genuinely don't understand by now what it is that you do
that pisses people off, find someone you trust and get them to explain it
to you.  I've tried.  Other people have tried.  You react by dismissing
and insulting us, then pretending months later that you've done nothing
wrong.  Now you've pissed off Linus and he has ultimate power to decide to
accept your pull requests or not ... and he's decided not to.  You had
a lot of chances to fix your behaviour before it got to this point.
It's sad that you chose not to take any of them.

Can you really not see the difference between, eg Palmer's response here:
https://lore.kernel.org/lkml/mhng-655602B8-F102-4B0F-AF4A-4AB94A9F231F@Palmers-Mini.rwc.dabbelt.com/

and your response whenever Linus dares to critique even the smallest
parts of your pull requests?

[pointless attempt to divert the conversation to engineering snipped]

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ