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: <tthojw6lkixjj5ackld7mjhmceffoxndpwmmgubo7gq3aclmzh@k5j2h4yfsuly>
Date: Mon, 11 Aug 2025 21:08:49 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Konstantin Shelekhin <k.shelekhin@...l.net>
Cc: admin@...inas.su, linux-bcachefs@...r.kernel.org, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, list-bcachefs@...lthompson.net, 
	malte.schroeder@...ip.de, torvalds@...ux-foundation.org
Subject: Re: [GIT PULL] bcachefs changes for 6.17

On Tue, Aug 12, 2025 at 12:04:53AM +0300, Konstantin Shelekhin wrote:
> On 11/08/2025 17:26, Kent Overstreet wrote:
> 
> > Konstantin, please tell me what you're basing this on.
> 
> This, for example: -
> https://lore.kernel.org/all/9db17620-4b93-4c01-b7f8-ecab83b12d0f@kernel.dk/
> - https://lore.kernel.org/all/20250308155011.1742461-1-kent.overstreet@linux.dev/
> I've just lurked around lore for a couple of minutes.

So for the dm-faulty one - md-flakey was removed without anyone ever
testing the equivalent functionality in the replacement - it was pretty
disruptive.

I'll fill you in on the other one off list, the tensions behind that
flare up go back years, and I don't think anyone wants that stuff
dredged up yet again on the list - Christoph and I in particular have
been quite frosty to each other at times, but we've always respected
each other and lately I think we've both made signs that we're actually
trying to work better together.

> > - and reference to an incident at LSF, but the only noteworthy event
> >  that I can recall at the last LSF (a year and a half ago) was where a
> >  filesystem developer chased a Rust developer out of the community.
> > 
> > So: what am I supposed to make of all this?
> 
> That you're trying to excuse your communication issues with other people's
> communication issues?

No, definitely not.

I don't think endlessly rehashing old stuff really solves anything. When
tensions are high, I try to narrow the focus and just focus on the work
at hand.

But the only thing I've found that really solves things in the long run
is just - talking. Talking when there isn't work hanging over our heads
that needs to be focused on, talking and listening without making
demands and trying to actually understand each other's points of view.