exclusive_lock::Policy::lock_requested() isn't guaranteed to queue
the release of exclusive lock (and in fact only one of the two existing
implementations does that). Instead of talking about the lock, log the
response to the notification.
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
return true;
}
- ldout(m_image_ctx.cct, 10) << this << " queuing release of exclusive lock"
- << dendl;
+ // potentially queue release of exclusive lock
r = m_image_ctx.get_exclusive_lock_policy()->lock_requested(
payload.force);
}
+ ldout(m_image_ctx.cct, 10) << this << " responding with r=" << r << dendl;
encode(ResponseMessage(r), ack_ctx->out);
}
return true;