linux-kernel - Re: [GIT PULL] bcachefs fixes for 6.11-rc5

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: <bczhy3gwlps24w3jwhpztzuvno7uk7vjjk5ouponvar5qzs3ye@5fckvo2xa5cz>
Date: Fri, 23 Aug 2024 23:10:47 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.11-rc5

On Sat, Aug 24, 2024 at 10:57:55AM GMT, Linus Torvalds wrote:
> On Sat, 24 Aug 2024 at 10:48, Kent Overstreet <kent.overstreet@...ux.dev> wrote:
> >
> > Sure, which is why I'm not sending you anything here that isn't a fix
> > for a real issue.
> 
> Kent, bugs happen.

I _know_.

Look, filesystem development is as high stakes as it gets. Normal kernel
development, you fuck up - you crash the machine, you lose some work,
you reboot, people are annoyed but generally it's ok.

In filesystem land, you can corrupt data and not find out about it until
weeks later, or _worse_. I've got stories to give people literal
nightmares. Hell, that stuff has fueled my own nightmares for years. You
know how much grey my beard has now?

Which is why I have spent many years of my life building a codebase and
development process where I can work productively where I can not just
catch but recover from pretty much any fuckup imaginable.

Because peace of mind is priceless...