From: Josef Bacik <josef@toxicpanda.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 10:46:04 -0400 [thread overview]
Message-ID: <20250627144441.GA349175@fedora> (raw)
In-Reply-To: <ahdf2izzsmggnhlqlojsnqaedlfbhomrxrtwd2accir365aqtt@6q52cm56jmuf>
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 the numbers don't lie.
josef@fedora:~/linux$ git tag --contains 1c6fdbd8f2465ddfb73a01ec620cbf3d14044e1a | grep -v rc > bcachefs-tags
josef@fedora:~/linux$ git tag --contains be0e5c097fc206b863ce9fe6b3cfd6974b0110f4 | grep -v rc > tags
josef@fedora:~/linux$ for i in $(cat tags); do git log --no-merges --oneline $i-rc2..$i fs/btrfs | wc -l; done > btrfs-counts.txt
josef@fedora:~/linux$ for i in $(cat bcachefs-tags); do git log --no-merges --oneline $i-rc2..$i fs/bcachefs | wc -l; done > bcachefs-counts.txt
josef@fedora:~/linux$ R -q -e "x <- read.csv('btrfs-counts.txt', header = F); summary(x); sd(x[ , 1 ])"
> x <- read.csv('btrfs-counts.txt', header = F); summary(x); sd(x[ , 1 ])
V1
Min. : 0.00
1st Qu.:10.25
Median :19.00
Mean :20.48
3rd Qu.:27.50
Max. :55.00
[1] 11.77108
>
josef@fedora:~/linux$ R -q -e "x <- read.csv('bcachefs-counts.txt', header = F); summary(x); sd(x[ , 1 ])"
> x <- read.csv('bcachefs-counts.txt', header = F); summary(x); sd(x[ , 1 ])
V1
Min. : 0.00
1st Qu.: 38.50
Median : 70.00
Mean : 63.86
3rd Qu.: 81.50
Max. :137.00
[1] 45.28218
>
So even including the wilder times of kernel development in general and btrfs's
specifically, our worst window was 55 patches, less than your mean.
These are not the same thing. Do not equivicate the two. Sterba is a phenomenal
maintainer who does his job well, manages to work with Linus just fine. We are
not the same, we do not work the same, and we absolutely do follow the rules, as
do 99.99% of the kernel community.
If xfs has done this then good for them. Those developers have a track record of
doing the right thing over a long period of time. Btrfs for sure hasn't. Thanks,
Josef
next prev parent reply other threads:[~2025-06-27 14:46 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 [this message]
2025-06-28 1:59 ` Theodore Ts'o
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=20250627144441.GA349175@fedora \
--to=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