Repository navigation
Add unit test that Subspace::range() owns its key memory - #14336
Merged
akshay-v-kaushik merged 1 commit intoOct 22, 2026
Merged
Conversation
Resolves the FIXME in Subspace::range(): verify the returned KeyRange remains valid after the Subspace that produced it is destroyed.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
nos-a
approved these changes
Oct 21, 2026
Contributor
Result of foundationdb-pr-clang-ide on Linux RHEL 9
|
Contributor
Result of foundationdb-pr-macos-m1 on macOS 14.x
|
Contributor
Result of foundationdb-pr-clang on Linux RHEL 9
|
Contributor
Result of foundationdb-pr-clang-arm on Linux RHEL 9
|
Contributor
Result of foundationdb-pr on Linux RHEL 9
|
Contributor
Result of foundationdb-pr-macos on macOS 14.x
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux RHEL 9
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem:
Subspace::range()infdbclient/Subspace.cpphad a FIXME: "test that this uses the keyRange arena and doesn't create another one". The returnedKeyRangepoints at its begin/end bytes. Those bytes must live in the range's own arena. If they lived in another arena, freed whenrange()returns, the range would dangle.Fix: The code already allocates from
keyRange.arena(), so no behavior change. The fix is to add a test that locks this in, and remove the FIXME.Problem:
Subspace::range()infdbclient/Subspace.cpphad a FIXME: "test that this uses the keyRange arena and doesn't create another one". The returnedKeyRangepoints at its begin/end bytes. Those bytes must live in the range's own arena. If they lived in another arena, freed whenrange()returns, the range would dangle.Fix: The code already allocates from
keyRange.arena(), so no behavior change. The fix is to add a test that locks this in, and remove the FIXME.The testing
New test:

/fdbclient/Subspace/rangeOwnsMemory. It callsrange(), destroys theSubspace, then checks that begin and end have the right bytes and that the range's arena holds them.Failure scenario tested: I temporarily made
range()allocate from a localArenainstead ofkeyRange.arena(). The test failed, so it catches the bug. The mutation was then reverted.