Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hammer: osd: hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared #5890

Merged
1 commit merged into from Nov 10, 2015

Conversation

Abhishekvrshny
Copy link

@ghost
Copy link

ghost commented Sep 15, 2015

@Abhishekvrshny could you git commit --amend and re-push ? Just for the sake of re-triggering the bot. I think this is a false negative.

Otherwise, the is_active() checks in the hitset code can erroneously
return true firing off repops stamped with the new epoch which then get
cleared in the map change code.  The filestore callbacks then pass the
interval check and call into a destroyed repop structure.

Fixes: 12809
Backport: hammer,firefly
Signed-off-by: Samuel Just <sjust@redhat.com>
(cherry picked from commit 14e02bc)
ghost pushed a commit that referenced this pull request Oct 2, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost pushed a commit that referenced this pull request Oct 3, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost pushed a commit that referenced this pull request Oct 3, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost pushed a commit that referenced this pull request Oct 3, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost pushed a commit that referenced this pull request Oct 7, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost pushed a commit that referenced this pull request Oct 8, 2015
… map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost
Copy link

ghost commented Nov 4, 2015

@liewegas does this backport look good to merge ? It passed a run of the hammer rados suite ( see http://tracker.ceph.com/issues/13356#note-11 and for details ).

@liewegas
Copy link
Member

liewegas commented Nov 6, 2015

👍

ghost pushed a commit that referenced this pull request Nov 10, 2015
hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Sage Weil <sage@redhat.com>
@ghost ghost merged commit e133ddc into ceph:hammer Nov 10, 2015
ghost pushed a commit that referenced this pull request Nov 17, 2015
hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Sage Weil <sage@redhat.com>
ghost pushed a commit that referenced this pull request Nov 17, 2015
hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Sage Weil <sage@redhat.com>
ghost pushed a commit that referenced this pull request Nov 17, 2015
hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared

Reviewed-by: Sage Weil <sage@redhat.com>
@ghost ghost changed the title hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared hammer: osd: hit set clear repops fired in same epoch as map change -- segfault since they fall into the new interval even though the repops are cleared Feb 18, 2016
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants