[PATCH ceph v2 0/1] backport fix for EC truncate+write planning corrupting shards

[Kefu Chai <k.chai@proxmox.com>]

v2: add the missing "ceph" project tag to the subject (was posted as a
bare "[PATCH]" in v1: 20260812082022.2910768-1-k.chai@proxmox.com).
No code change from v1 (range-diff confirms the patch is byte-identical).

Ceph 20.2.1 and 20.2.2 both carry a regression in EC shard-size
planning for truncate+write transactions on pools with
allow_ec_optimizations: affected objects fail decode with a
ceph_assert on read, and since recovery reads hit the same code path,
OSDs crash-loop on startup and the damage follows PG remapping
(https://tracker.ceph.com/issues/77276,
https://tracker.ceph.com/issues/78400). The stored shards themselves
stay intact (this is a read-path assertion, not silent data
corruption), but a crash-looping OSD that takes an EC pool inactive is
a production problem, and it's already hit at least one reported
deployment (see tracker #78400 note 7 for interim recovery guidance
for anyone affected before the fix ships).

The upstream fix (a1bb747293b) landed in Tentacle after 20.2.2 was
already tagged, so it will only ship with the next ceph point release.
This backports the single commit ahead of that so our packaging isn't
carrying the regression in the meantime.

Given the production impact, please consider this for the next point
release / repository push.

Kefu Chai (1):
  backport fix for EC truncate+write planning corrupting shards

 ...n-fix-truncate-write-planning-for-EC.patch | 128 ++++++++++++++++++
 patches/series                                |   1 +
 2 files changed, 129 insertions(+)
 create mode 100644 patches/0014-osd-ECTransaction-fix-truncate-write-planning-for-EC.patch

-- 
2.47.3