From: "Theodore Ts'o" <tytso@mit.edu>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kerenl@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc4
Date: Fri, 27 Jun 2025 21:59:34 -0400 [thread overview]
Message-ID: <20250628015934.GB4253@mit.edu> (raw)
In-Reply-To: <20250627144441.GA349175@fedora>
On Fri, Jun 27, 2025 at 10:46:04AM -0400, Josef Bacik wrote:
> On Thu, Jun 26, 2025 at 10:22:52PM -0400, Kent Overstreet wrote:
> > per the maintainer thread discussion and precedent in xfs and btrfs
> > for repair code in RCs, journal_rewind is again included
>
> I'm replying to set the record straight. This is not the start of the
> discussion. I am not going to let false statements stand by unchallenged
> however.
>
> Sterba has never sent large pull requests in RCs, certainly not with
> features in them. Even when Chris was the maintainer and we were a
> little faster and looser and were pushing the envelope to see what
> Linus would accept we didn't ship anything near this volume of
> patches past rc1.
And as far as XFS is concerned, "citation needed". Dave Chinner (who
is not the current XFS maintainer) has asserted that there might be a
time when XFS *might* want to send repair code post merge window.
However, I'm not aware of any time when Darrick Wong was working on
XFS online repair that he sent changes outside of the merge window as
the XFS maintainer.
And now that XFS online repair feature is upstream, *bug fixes* can be
sent at any time. So (a) I am not aware of any time that XFS *has*
sent online repair changes upstream outside of a merge window --- this
is just an assertion by Kent --- and (b) I am not sure when XFS would
need to send some kind of new feature involving online repair
upstream, given that online repair is *already* upstream.
- Ted
prev parent reply other threads:[~2025-06-28 1:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 2:22 [GIT PULL] bcachefs fixes for 6.16-rc4 Kent Overstreet
2025-06-27 3:21 ` Linus Torvalds
2025-06-27 3:34 ` Kent Overstreet
2025-07-01 14:43 ` John Stoffel
2025-07-02 16:34 ` Kent Overstreet
2025-07-02 17:41 ` Carl E. Thompson
2025-07-02 17:53 ` Kent Overstreet
2025-07-02 18:49 ` Malte Schröder
2025-07-07 20:03 ` John Stoffel
2025-07-07 20:39 ` Kent Overstreet
2025-07-07 21:32 ` Carl E. Thompson
2025-07-04 7:02 ` Hillf Danton
2025-06-27 19:07 ` Kyle Sanderson
2025-06-27 19:16 ` Kyle Sanderson
2025-06-27 19:42 ` Kent Overstreet
2025-06-28 8:06 ` Gerhard Wiesinger
2025-06-27 3:33 ` pr-tracker-bot
2025-06-27 14:46 ` Josef Bacik
2025-06-28 1:59 ` Theodore Ts'o [this message]
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=20250628015934.GB4253@mit.edu \
--to=tytso@mit.edu \
--cc=josef@toxicpanda.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kerenl@vger.kernel.org \
--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).