box: fix invalid memory access in tuple_compare_with_key_sequential
Since number type was introduced we can not assume if tuples are equal by comparison then their sizes are equal too. So the place the assumption is used is fixed. Closes #8899 NO_DOC=bugfix (cherry picked from commit f4de9faf)
Showing
- changelogs/unreleased/gh-8899-compare-with-key-slowpath-invalid-memory-access.md 4 additions, 0 deletions...h-8899-compare-with-key-slowpath-invalid-memory-access.md
- src/box/tuple_compare.cc 3 additions, 7 deletionssrc/box/tuple_compare.cc
- test/box-luatest/gh_8899_tuple_compare_with_key_slowpath_last_loop_test.lua 41 additions, 0 deletions...h_8899_tuple_compare_with_key_slowpath_last_loop_test.lua
Loading
Please register or sign in to comment