On Mon, Aug 03, 2026 at 10:24:10PM +0800, Ming-Hung Tsai wrote: > The fix addresses more than crafted metadata. A lost write on disk > drives can cause a stale block that was freed as a hint block, > triggering this out-of-bounds access issue.
You're right, and the commit message claims the opposite. Its last sentence should read: Arrays only ever read their own blocks, so a mismatch means the block is not one this array wrote: a crafted image, or a lost write leaving a stale block that was freed as a hint block. Mikulas, that is a message-only change -- fold it in when applying if you agree. Bryam
