Actions
Bug #9143
closedIncorrect key sequence in encoding object name to key for GenericObjectMap
% Done:
0%
Source:
Community (user)
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
For example, two oid has same hash and their name is:
A: "rb.data.123"
B: "rb-123"
In ghobject_t compare level, A < B. But GenericObjectMap encode "." to
"%e", so the key in DB is:
A: GHOBJTOSEQ:blah!51615000!!none!!rb%edata%e123!head
B: GHOBJTOSEQ:blah!51615000!!none!!rb-123!head
A > B
And it seemed that the escape function is useless and should be disabled.
Updated by Greg Farnum over 9 years ago
How did you run across this? Is it feasible to fix it by typing the escaped strings and writing a custom comparator?
Actions