linux-kernel - Re: [GIT PULL] bcachefs fixes for 6.16-rc3

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: <20250620124346.GB3571269@mit.edu>
Date: Fri, 20 Jun 2025 08:43:46 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Martin Steigerwald <martin@...htvoll.de>,
        Jani Partanen <jiipee@...apeli.fi>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-bcachefs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc3

On Fri, Jun 20, 2025 at 04:14:24AM -0400, Kent Overstreet wrote:
> 
> There is a time and a place for rules, and there is a time and a place
> for using your head and exercising some common sense and judgement.
> 
> I'm the one who's responsible for making sure that bcachefs users have a
> working filesystem. That means reading and responding to every bug
> report and keeping track of what's working and what's not in
> fs/bcachefs/. Not you, and not Linus.

Kent, the risk as always of adding features after the merge window is
that you might introduce regressions.  This is especially true if you
are making changes to relatively sensitive portions of any file system
--- such as journalling.

The rules around the merge window is something which the vast majority
of the kernel developers have agreeded upon for well over a decade.
And it is Linus's responsibility to *enforce* those rules.

If, as you say, bcachefs is experimental, and no sane person should be
trusting their data on it, then perhaps this shouldn't be urgent.  On
the flip side, perhaps if you are claiming that people should be using
it for critical data, then perhaps your care for user's data safety
should be.... revisted.

Cheers,

						- Ted