]> git.apps.os.sepia.ceph.com Git - ceph.git/commit
librbd: properly handle potential object map failures 24179/head
authorJason Dillaman <dillaman@redhat.com>
Tue, 18 Sep 2018 18:37:12 +0000 (14:37 -0400)
committerJason Dillaman <dillaman@redhat.com>
Thu, 20 Sep 2018 16:43:11 +0000 (12:43 -0400)
commit765f8ce2536b315a046d0aceff234e9e3c66271f
treeabe1937925fa052d1c510d1fe0100e4800c03628
parente86898a7f5f2f35d36e5a259a4446d9ff7d971ce
librbd: properly handle potential object map failures

Remove the "ceph_assert" statements and instead bubble any potential
error code up to the caller. The object map state machines should
attempt to return a 0 upon failure unless it was unable to flag the
object map as invalid.

Fixes: http://tracker.ceph.com/issues/36074
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
21 files changed:
src/librbd/DeepCopyRequest.cc
src/librbd/deep_copy/ObjectCopyRequest.cc
src/librbd/deep_copy/SnapshotCopyRequest.cc
src/librbd/exclusive_lock/PostAcquireRequest.cc
src/librbd/exclusive_lock/PreReleaseRequest.cc
src/librbd/image/RefreshRequest.cc
src/librbd/io/CopyupRequest.cc
src/librbd/io/ObjectRequest.cc
src/librbd/object_map/InvalidateRequest.cc
src/librbd/object_map/RefreshRequest.cc
src/librbd/object_map/Request.h
src/librbd/object_map/SnapshotRemoveRequest.cc
src/librbd/operation/ResizeRequest.cc
src/librbd/operation/SnapshotCreateRequest.cc
src/librbd/operation/SnapshotRollbackRequest.cc
src/test/librbd/deep_copy/test_mock_ObjectCopyRequest.cc
src/test/librbd/exclusive_lock/test_mock_PostAcquireRequest.cc
src/test/librbd/image/test_mock_RefreshRequest.cc
src/test/librbd/io/test_mock_ObjectRequest.cc
src/test/librbd/object_map/test_mock_RefreshRequest.cc
src/test/librbd/test_mock_DeepCopyRequest.cc