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: <5ip2wzfo32zs7uznaunpqj2bjmz3log4yrrdezo5audputkbq5@uoqutt37wmvp>
Date: Sat, 9 Aug 2025 19:13:55 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Matthew Wilcox <willy@...radead.org>
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 Sun, Aug 10, 2025 at 12:01:18AM +0100, Matthew Wilcox wrote:
> 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]

There's been pull requests where I've quietly dropped patches and
respun. I've never argued with Linus when it comes to other subsystems,
and there are things I've absolutely changed and addressed about the
bcachefs pull requests (e.g. switching to sending them on Thursdays;
which, unfortunately, took a three day shouting match before it came out
that that was the issue).

But when it comes to getting bugfixes out that users are waiting on; too
many of the pull requests have come over that, and "feedback" on those
has never come in the form of "do we need this? Can we dial things
back?" - too often it's been "oh hell no!"; and when I've got users I'm
supporting that's just not going to go well. Nor is it how things
generally work for other subsystems; Linus at one point gave me examples
of his other pull request feedback, while saying "this is totally
normal" - and my immediate response was, if I'd been getting that kind
of calm reasonable feedback, we'd have been in a very different place.

And you recently took to outright swearing at me on IRC, while I've been
staring at mm bugs and going "ok, the CONFIG_VM_DEBUG approach isn't
working".

And now, I just got an email from Linus saying "we're now talking about
git rm -rf in 6.18", after previously saying we just needed a
go-between.

So if that's the plan, I need to be arguing forcefully here, because a
lot is on the line for a lot of people.

I've heard from so many people saying things along the lines of "when
will it be ready, I _need_ something more reliable because I've been bit
too many times", and up until a month ago I've been telling people
"check back, we're nearly there, but check back soon".

Now, I finally clear out the bug tracker, and the bug reports and
feedback start pointing to "yes, we're pretty much there", and I have
this to face.

Oi vey.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ