snabelen.no er en av mange uavhengige Mastodon-servere du kan bruke for å delta i det desentraliserte sosiale nettet.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

384
aktive brukere

#bcachefs

3 innlegg3 deltakere0 innlegg i dag

We're a week and a half into the 6.17 #Linux kernel merge window and #bcachefs has neither been removed nor have the queued patches been merged.

Today Alex Galvin asked Linus to clarify his future stance on this, with Kent Overstreet immediately weighing in in his usual manner. Linus didn't respond so far, but if there may have been a slim chance of him backing down, I think Overstreet has again pushed all the necessary buttons to not make that happen.

spinics.net/lists/kernel/msg57

Som svar til Sturmflut

@Sturmflut I might be wrong, but I don't think that "threatening to declare #bcachefs stable" makes much of a difference – or even is a reason to throw it out now.

Just look at how many changes "stable" file systems btrfs, ext4, xfs et. al. merge each cycle – which is why it's important that they follow the rules and understand the development process. Kent showed to not play by those rules multiple times; so it's better for everyone to throw it out now before it is declared "stable".

But whatever, what I think doesn't matter, we'll just have to wait and see what Linus will do.

@kernellogger I think Overstreet "threatening" to declare #bcachefs stable in 6.18 raises a lot of questions Torvalds can't/doesn't want to answer in a whim while merging so many other patchsets. Considering he also announced to be traveling a lot next month and maybe having to push back 6.17-rc1, he may simply decide to ignore Overstreet for a full kernel release (like last year with #Linux 6.13) and deal with it later.

(I would.)

A small indicator regarding the uncertain future[1] of #bcachefs in mainline #Linux that might or might not mean something:

Linus worked through quite a few pull requests with updates for various filesystems[2] and a lot of vfs stuff for #Linux 6.17, but for now ignored the one from Kent with the bcachefs updates:

lore.kernel.org/all/22ib5scviw (in which Kent announced plans to remove the experimental label for 6.18)

[1] hachyderm.io/@kernellogger/114

[2] see:
hachyderm.io/@kernellogger/114
hachyderm.io/@kernellogger/114
hachyderm.io/@kernellogger/114
hachyderm.io/@kernellogger/114
mastodon.social/@andyprice/114
git.kernel.org/torvalds/c/f3f5

Look like @torvalds might remove #bcachefs from the #Linux with version 6.17:

lore.kernel.org/all/CAHk-=wi+k

'"I have pulled this, but also as per that discussion, I think we'll be parting ways in the 6.17 merge window."'

Backstory that triggered this can be found here:

lore.kernel.org/all/CAHk-=wi2a

To quote from there:

'"You seem to have forgotten what the point of the merge window was again.

We don't start adding new features just because you found other bugs.

[…]

Make the -rc fixes be pure fixes.

Linus"'

Highlights from the main #bcachefs merge for #Linux 6.16: git.kernel.org/torvalds/c/5225

- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.

- Various changes to support deployable disk images

- Major error message improvements for btree node reads, data reads, and elsewhere.

- New option, 'rebalance_on_ac_only'.

- Repair/self healing:

- We can now kick off recovery passes and run them in the background if we detect errors.

- Performance:

- Faster snapshot deletion

- Faster device removal

- We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.

- Stack usage improvements: All allocator state has been moved off the stack

git.kernel.orgMaking sure you're not a bot!