Merge branches (11 topics incl. logical-ino-costs) into misc-next/testing
2026-09-21: misc-next/topics/logical-ino-costs combines the former
backref-hang, delayed-ref-fixes and logical-ino topics into one three-patch
series (reducing LOGICAL_INO costs): the add_all_parents() rewind-cycle
hang, the quadratic delayed-ref merge walk, and
BTRFS_LOGICAL_INO_ARGS_COMMIT_ROOT. Tree unchanged by the restructure.
topics/stripe-alloc is the 2026-09-19 restructure: nine folds, the mount
option erased from history, the property patch moved to #4, plus system
chunks under stripe_meta (65 patches).
Also merges 'misc-next/topics/low-space' (topics/low-space: generic low-space behaviour improvements (reclaim errno)).
Integration of topics/low-space with topics/stripe-alloc, in block-group.c
and space-info.c (octopus only from 2026-09-29; since 2026-10-29 it lives in
topics/low-space, which is restacked on topics/stripe-alloc: "btrfs: hold
block groups free for relocation" carries it; Zygo: "they all have to be
submitted in some order as patches, not merges"):
- a group held for relocation counts only its claimable whole stripes
as reserve (resynced at each commit-time stripe rescan); its trapped
space is in bytes_stripe_unusable already, and counting it twice made
the metadata space_info read over-full on a full raid6 filesystem;
- ordinary data writers' whole-stripe admission excludes the held
groups' stripes; relocation still sees them.
stripe_meta's bytes_stripe_reserve is NOT reduced by the held groups: it
is an admission margin that keeps tree blocks off the reserve's emergency
fallback, and without it a metadata fill consumed the reserve before any
relocation (dhive sresmn raid5/raid5, 2026-09-29).
Also merges 'misc-next/topics/dedupe-mtime' (topics/dedupe-mtime: don't update mtime and ctime when deduping a range ending in a hole).
Also merges 'misc-next/topics/dm-stripfault' (topics/dm-stripfault: the stripfault dm target, a raid56 RMW test fixture; drop before upstream).
Also merges 'misc-next/topics/allocator-hints' (topics/allocator-hints: Kai
Krakow's allocator hint series, as on the 6.18 lane with the no-transaction
type store (v2b), replacing the four hint patches formerly carried on
zygo-misc-next-zb64, whose type store deadlocked against device remove).
Ported onto misc-next: btrfs_update_device() is already non-static
upstream (prototype not re-added), and BTRFS_DEV_STATE_TYPE_DIRTY is bit 8
because misc-next uses 6 and 7 (FLUSH_FAILED, ITEM_FOUND).
Also merges 'misc-next/topics/read-policies' (topics/read-policies: Kai
Krakow's read policies and per-device read stats: CONFIG_BTRFS_READ_POLICIES,
queue and queue-adaptive policies, CONFIG_BTRFS_PER_DEVICE_IO_STATS).
Ported onto misc-next: no offload_csum_mode (gone upstream), sysfs.c
includes <linux/string_choices.h> instead of <crypto/hash.h>.
Kconfig and sysfs.c conflicts with allocator-hints resolved as the union,
as on 6.18.
2026-10-07: rebased onto kdave misc-next
9f11e00e8027 ("btrfs: stop reading free space inodes from the commit root"), which kdave force-updated
onto a later 7.3-rc base. Dropped from topics/raid56-fixes: "btrfs: raid56: do
not verify the content if there is no data checksum" (upstream
05d60d2ee801a).
Both stripe-alloc conflicts and the octopus conflict are Boris Burkov's SYSTEM
space change (
e518b02aa180b): our stripe headroom folded into need_system_chunk,
our relocation-reserve bail-out unioned with the system-space one.
2026-10-10 (Zygo): dropped topics/raid6-fixes. Upstream
49ba3a3c0d67
("btrfs: disguise single-data-RAID56 as RAID1/RAID1C3") maps 3-device RAID6
chunks as RAID1C3, so btrfs never calls lib/raid6 with three disks, and lib/raid6
now treats fewer than RAID6_MIN_DISKS (4) as unsupported.
2026-10-10: topics/stripe-alloc gains the 2026-10-09 review (26 patches):
fixes for the review findings F01-F14 and M01-M12 (run owner keyed by
subvolume, ended ordered extents marked written, unused-group cleanup with
open runs, commit-time and read-only metadata drains without timeout
escapes, stats removals), the comment cleanup, the unwritten-on-end log,
and skipping single-data-stripe RAID5/6 groups with their free space
counted in write admission. Validated on cand/review-1009/misc-next-zb64
df9f142b8b87: KASAN sanity + directed and full r6c3.
2026-10-11: topics/stripe-alloc gains "account claimable stripes while a
trim has them out" (1 patch): fstrim and async discard took free ranges
out of the tree without touching stripe_claimable, so a rescan in the
window found the incremental count above its scan. Validated on
cand/trimclaim2/misc-next-zb64
f412553a1ea9: KASAN directed
(incl. trim-claimable-race-test), claimable solo, corrupt-churn x3 (6.18).
2026-10-16: + misc-next/topics/replace-fixes (commit the canceled state when a device replace fails or is canceled).
2026-10-17: the raid56 scrub/replace commits move from
misc-next/topics/raid56-fixes to a new misc-next/topics/raid56-scrub-replace, in safe order:
per-row parity check (unrepaired full stripes still fail with -EIO),
copy original parity of unrepairable rows to the replace target, copy
unrepaired data sectors, copy every sector of raid56 data stripes, avoid
the replace source only for its own stripes, read no-extent sectors from
the replace source, and last the return-0 flip, so there is no bisect
window where replace silently drops P/Q. misc-next/topics/replace-fixes gains
the dev-replace error-accounting series (uncorrectable read and target
write error counts, cancel progress, resumed-replace WARN fix) and the
ABORT_ON_UNCORRECTABLE start flag. Tree identical to the tested
candidate refs/cand/r5fix-mn/testing.
2026-10-17 (Zygo): misc-next/topics/raid56-scrub-replace now starts with a copy of
Filipe Manana's "btrfs: scrub: fix lost error return value when scrubbing
raid56 parity stripe" (btrfs/for-next
ec0795c045c3, verbatim), so the rebase
drops it once it is in the base. Tree unchanged.
Also merges 'misc-next/topics/dev-stats' (topics/dev-stats: write dirty device stats when no transaction is running; a behaviour change reviewers may reject, kept droppable on its own).
Also merges 'misc-next/topics/resize-missing' (topics/resize-missing: allow shrinking a missing device so a smaller replacement fits; Qu Wenruo's 2019 patch, rewritten).
Merge topic read-repair-fixes (repair bio end_io for submit failures)
Also merges 'misc-next/topics/reflink-inline-fixes' (copy_inline_to_page() fixes:
zeroing offset in large folios/subpage, decompression error path).
Candidate: + wbkick v5 (stripe-alloc: whole-range writeback under stripe_alloc,
carry qgroup fold, fsleak fold, stripe_whole_bytes removal).
Also merges misc-next/topics/reclaim-fixes (topics/reclaim-fixes: generic block group
reclaim fixes split out of topics/stripe-alloc; its tip is an ancestor of
that topic, so it adds no tree change of its own).
2026-10-30 (Zygo 2026-10-29 rulings, restructure1030; tree unchanged but for the
BTRFS_DEBUG=n build fix folded into "optionally audit data
read-modify-writes against the committed extent tree"):
+ misc-next/topics/test-knobs, stacked on topics/stripe-alloc like a test
fixture: the reclaim exclusive-operation gap (from topics/reclaim-fixes)
and the rbio cache size debug knob (from topics/raid56-fixes), both
DO-NOT-UPSTREAM; the knob now carries its integration with stripe-alloc's
rbio pins and cache prune. topics/raid56-scrub-replace is restacked on
topics/read-repair-fixes, which now precedes it here; the abort gate
interplay (parity scrub reporting and counting, rebuilt-data writes) is
in its commits instead of this merge. deadlock-fixes: the relock fix is
folded into "never block on space reservations ...".
Commit messages fixed in stripe-alloc, raid56-scrub-replace and
allocator-hints.
2026-10-30 (Zygo-approved, knobmv1030): in topics/test-knobs' rbio cache size
knob and in this merge, the knob's 3-line btrfs_set_rbio_cache_size()
declaration in raid56.h moves from above raid56-fixes'
btrfs_raid56_uncache_range() to after btrfs_rbio_unpin_stale(), so the
export's revert of the knob from testing applies cleanly. No other change.