librbd: don't hold owner_lock for validate_image_removal()

handle_exclusive_lock() and handle_shut_down_exclusive_lock() call
validate_image_removal() without owner_lock held, so holding it in
shut_down_exclusive_lock() appears to be redundant.

Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
(cherry picked from commit b1bf3eaef200fb5d1aa847cad14936f2bbbf7b64)

diff --git a/src/librbd/image/PreRemoveRequest.cc b/src/librbd/image/PreRemoveRequest.cc
index 3ad92616af0005f3a05d0396818e500177ec1fd3..fa4141834b186c3b2a338363a638eef503abb3c7 100644 (file)
--- a/src/librbd/image/PreRemoveRequest.cc
+++ b/src/librbd/image/PreRemoveRequest.cc
@@ -117,8 +117,9 @@ void PreRemoveRequest<I>::handle_exclusive_lock(int r) {
 
 template <typename I>
 void PreRemoveRequest<I>::shut_down_exclusive_lock() {
-  std::shared_lock owner_lock{m_image_ctx->owner_lock};
+  std::shared_lock owner_locker{m_image_ctx->owner_lock};
   if (m_image_ctx->exclusive_lock == nullptr) {
+    owner_locker.unlock();
     validate_image_removal();
     return;
   }