From: "Theodore Ts'o" <tytso@mit.edu>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Martin Steigerwald <martin@lichtvoll.de>,
Jani Partanen <jiipee@sotapeli.fi>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc3
Date: Fri, 20 Jun 2025 08:43:46 -0400 [thread overview]
Message-ID: <20250620124346.GB3571269@mit.edu> (raw)
In-Reply-To: <hewwxyayvr33fcu5nzq4c2zqbyhcvg5ryev42cayh2gukvdiqj@vi36wbwxzhtr>
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
next prev parent reply other threads:[~2025-06-20 12:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 23:06 [GIT PULL] bcachefs fixes for 6.16-rc3 Kent Overstreet
2025-06-20 0:51 ` Linus Torvalds
2025-06-20 1:09 ` Kent Overstreet
2025-06-20 1:25 ` Jani Partanen
2025-06-20 1:51 ` Kent Overstreet
2025-06-20 7:12 ` Martin Steigerwald
2025-06-20 7:27 ` Martin Steigerwald
2025-06-20 8:14 ` Kent Overstreet
2025-06-20 12:43 ` Theodore Ts'o [this message]
2025-06-20 15:17 ` Christoph Heinrich
2025-06-20 23:34 ` Kent Overstreet
2025-06-21 0:15 ` Kent Overstreet
2025-06-21 21:07 ` Jérôme Poulin
2025-06-21 22:50 ` Jérôme Poulin
2025-06-21 23:46 ` Kent Overstreet
2025-06-27 3:33 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250620124346.GB3571269@mit.edu \
--to=tytso@mit.edu \
--cc=jiipee@sotapeli.fi \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lichtvoll.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).