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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <01252d3a-1856-4e9e-a395-3f15c0a3afd0@proton.me>
Date: Fri, 06 Sep 2024 07:50:46 +0000
From: Nathan Owens <ndowens08@...ton.me>
To: Kent Overstreet <kent.overstreet@...ux.dev>, 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

Will say both Linus and Kent has their points and reasoning, but I must 
ask, Kent please stick with the guidelines of submitting fixes, 
features, etc. I would like that Bcachefs to stay in the kernel and see 
how well Bcachefs comes along in the future and when it has your 
features and ideas. One day I would like to maybe switch from BTRFS to 
Bcachefs when it gets more features and some of the things I would like 
to be able to do, like restore from snapshot and eventually boot to 
snapshots to restore a messed up system. If it gets taken out of the 
tree, less people will know about it, nor likely take the trouble of 
compiling a kernel for Bcachefs.

This comment is not bash either Linus or you Kent, but just a thought in 
hopes that more people will possibly switch to it and encourage 
production keeps happening as well.

On 8/23/24 10:10 PM, Kent Overstreet wrote:
> On Sat, Aug 24, 2024 at 10:57:55AM GMT, Linus Torvalds wrote:
>> On Sat, 24 Aug 2024 at 10:48, K
ent 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...
>

Download attachment "publickey - ndowens08@...ton.me -
 0x227C5078.asc" of type "application/pgp-keys" (701 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (250 bytes)