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

PGLog::rewind_divergent_log must not call mark_dirty_from on end() #366

Merged
merged 1 commit into from Jun 19, 2013
Merged

PGLog::rewind_divergent_log must not call mark_dirty_from on end() #366

merged 1 commit into from Jun 19, 2013

Conversation

ghost
Copy link

@ghost ghost commented Jun 19, 2013

PGLog::rewind_divergent_log is dereferencing iterator "p" though it is
already past the end of its container. When entering the loop for the
first time, p is log.log.end() and must not be dereferenced.

mark_dirty_from must only be called after p--. It
will not rewind past begin() because of the

if (p == log.log.begin())

test above.

http://tracker.ceph.com/issues/5398 fixes #5398

Signed-off-by: Loic Dachary loic@dachary.org

PGLog::rewind_divergent_log is dereferencing iterator "p" though it is
already past the end of its container. When entering the loop for the
first time, p is log.log.end() and must not be dereferenced.

mark_dirty_from must only be called after p--. It
will not rewind past begin() because of the

  if (p == log.log.begin())

test above.

http://tracker.ceph.com/issues/5398 fixes #5398

Signed-off-by: Loic Dachary <loic@dachary.org>
athanatos added a commit that referenced this pull request Jun 19, 2013
PGLog::rewind_divergent_log must not call mark_dirty_from on end()

Reviewed-by: Samuel Just <sam.just@inktank.com>
@athanatos athanatos merged commit 9056402 into ceph:master Jun 19, 2013
andriytk pushed a commit to andriytk/cortx-rgw that referenced this pull request Aug 31, 2022
…Tagging API. (ceph#366)

Problem:
Observed discrepancy with AWS for DeleteBucketTagging API.
In ceph-RADOS DeleteBucketTagging API returning status code=200
on success, while in AWS it is returning status code=204.

Solution:
Assign op_ret=STATUS_NO_CONTENT when DeleteBucketTagging operation
is successful.

Signed-off-by: Shriya Deshmukh <shriya.deshmukh@seagate.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant