{"thread":{"id":"65864","subject":"Re: [PATCH 11/11] reftable/table: fix OOB read on truncated table","startedAt":"2026-06-24T09:46:34Z","lastAt":"2026-06-24T09:46:34Z","messageCount":1,"participants":["Patrick Steinhardt"],"isPatch":true,"patchVersion":1,"patchTotal":11},"messages":[{"id":"546280","messageId":"ajuncy95aopgDt-b@pks.im","threadId":"65864","inReplyTo":"20260624181426.NJDNpVd1RE-qJjBVh5jtQg@awo.kakao.com","subject":"Re: [PATCH 11/11] reftable/table: fix OOB read on truncated table","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-06-24T09:46:27Z","receivedAt":"2026-06-24T09:46:34Z","isPatch":true,"body":"On Wed, Jun 24, 2026 at 06:14:26PM +0900, oxsignal wrote:\n> Hi Patrick,\n> \n> Thanks for the patch series, for adding the dedicated reftable fuzzer, and for\n> the credit.\n> \n> I reviewed the cover letter and the reftable hardening patches. Patch 05/11\n> matches the OOB write case I reported:\n> the new minimum block-size validation before handling the log block prevents\n> the bogus inflated-size underflow from reaching the inflate/copy path.\n> \n> The rest of the series also looks like a good cleanup of the corrupted reftable\n> parser surface, especially the restart-count/restart-offset and truncated-table\n> checks.\n> If I find any remaining malformed-table case that is not covered by this\n> series, I will follow up with the reproducer.\n> \n> Thanks again for handling this so quickly.\n\nPerfect, thanks for the report and reading through the patches!\n\nPatrick\n"}]}