[v25.1.x] storage: fix index state truncate overflow #26431
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #26051
Fixes #26193
CONFLICT:
Similar to #25979, when an index contains state that leads it to overflow, it is unreliable. In this case, this could affect truncation, and result in us removing incorrect index entries.
So, this makes the truncate avoid removing entries if this case is detected, with the expectation that no entries are added that have overflowed.
Note, this bug doesn't appear to be as severe as #25979 in that:
Nonetheless, some kind of fix seems appropriate because it's difficult to reason about the overflow otherwise.
(cherry picked from commit e882d67)
Backports Required
Release Notes