| compress-props, all phases | 6.18 #316 (bhive, ahive), misc-next #66 (dhive, ehive); KASAN inline + lockdep + BTRFS_ASSERT | PASS 66/66 on all four; X1 `zlib` 1245184 = zlib:3, X2 `zstd` 1024000 = zstd:15 (= ck1103) |
| rb1028-regress minus qu-p1 | #316 (bhive), #66 (dhive) | per-test verdicts identical to ck1103 (all PASS, retire-wait-abort SKIP 77) |
+## xf1106 (2026-11-06): stripe-alloc history change, trees identical
+
+stripe-alloc's extract-hook drop (ck1104) is now folded into the patches
+that add the stripe_alloc property handlers. The handlers never get an
+extract hook, and they are inserted after prop_compression_extract(), not
+next to the prototype line that patch 5 changes. The cover letter's merge
+note ("set no extract hook at all") is now true for every patch of that
+series. compress-fixes itself is unchanged. The testing octopus still
+merges with **no resolution** on both lanes: compress-fixes x stripe-alloc
+is clean as a 2-way merge, and props.c from the base by merge-file is clean
+in both orders and equals testing's (raid56-wh-harness
+`forensics/xf1106/oct-*.txt`).
+
## Not covered / open
- (Obsolete since rb1103: the patch that handled a parent directory
Kernel logs: no KASAN/WARN/BUG/lockdep/hung task/assertion; debug_locks 1,
taint 0. At the next export the commit folds into patches 4 and 40.
+## xf1106 (2026-11-06): the extract-hook drop folded into patches 4 and 40
+
+Zygo, 2026-11-06: fold patch 86 ("drop the extract hooks of the
+stripe_alloc properties") into the patches that add the hooks. This changes
+history only: every tree is identical (topic tip, low-space, test-knobs,
+testing, zb64, both lanes). Patch 4 ("control the policy with a filesystem
+property") no longer adds prop_stripe_alloc_extract() or its `.extract`
+line. It now inserts its stripe_alloc block after prop_compression_extract()
+instead of between the two compression hooks, so no patch moves upstream
+code. Patch 40 (allow-rmw) no longer adds prop_stripe_rmw_extract() or its
+`.extract` line. The commit messages are unchanged (neither mentions the
+hook). The series is one patch shorter (86 -> 85 in the next export).
+
+Checks (raid56-wh-harness `forensics/xf1106/`):
+- Per-commit content, authorship, dates and messages identical for every
+ replayed commit. Each target's +/- lines equal the old ones minus exactly
+ the hook.
+- No commit carries a stripe `.extract` hook.
+- A fresh octopus conflicts in the same pre-existing places as before; props.c
+ never conflicts, and compress-fixes still merges with no resolution.
+- Per-commit buildcheck of stripe-alloc, low-space and test-knobs on both
+ lanes: failed=0, no new warnings, tip links rc 0.
+- misc-next zb64 KASAN + lockdep + ASSERT #69 (md5
+ ed0b7198bf32294dbfa6b38034f46d4b) on dhive and ehive: boot log clean,
+ debug_locks 1.
+- No runtime tests, since the trees are identical.
+
+Promoted: 6.18 stripe-alloc 2fdb85cf927e, testing b7c35070837b, zb64
+bb52f0ff2398; misc-next stripe-alloc e77e4c9c2371, testing 3b5b4d424790,
+zb64 dcf19c743b68.
+
## Not covered / open
Patches without a test of their own (covered at most incidentally by the