jewel: msgr: don't truncate message sequence to 32-bits #12416
Merged
Conversation
This file contains 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
Message sequence is 64-bits number, but the upper 32-bits get lost when setting/getting message sequence. This causes messenger to malfunction after receiving 1^32 messages Fixes: http://tracker.ceph.com/issues/16122 Signed-off-by: Yan, Zheng <zyan@redhat.com> (cherry picked from commit d52832d)
ghost
changed the base branch from
smithfarm
changed the title
|
@tchaikov This passed a rados suite at http://tracker.ceph.com/issues/17851#note-45 with some (few, unrelated) failures as well as an fs suite at http://tracker.ceph.com/issues/17851#note-49 OK to merge? |
|
retest this please. |
smithfarm
changed the title
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.
http://tracker.ceph.com/issues/18219