librbd: disable automatic refresh of image upon lock message

There is no need to refresh the image upon request/release/acquire
of the exclusive lock.  The next IO or maintenance op will kick off
the refresh.  This is interfering with the refresh state machine
unit test case (since two concurrent refreshes shouldn't be possible).

Signed-off-by: Jason Dillaman <dillaman@redhat.com>
This commit is contained in:
Jason Dillaman 2016-05-02 10:33:50 -04:00
parent 608e098513
commit ee617a0ca5

View File

@ -92,7 +92,7 @@ enum NotifyOp {
struct AcquiredLockPayload {
static const NotifyOp NOTIFY_OP = NOTIFY_OP_ACQUIRED_LOCK;
static const bool CHECK_FOR_REFRESH = true;
static const bool CHECK_FOR_REFRESH = false;
ClientId client_id;
@ -106,7 +106,7 @@ struct AcquiredLockPayload {
struct ReleasedLockPayload {
static const NotifyOp NOTIFY_OP = NOTIFY_OP_RELEASED_LOCK;
static const bool CHECK_FOR_REFRESH = true;
static const bool CHECK_FOR_REFRESH = false;
ClientId client_id;
@ -120,7 +120,7 @@ struct ReleasedLockPayload {
struct RequestLockPayload {
static const NotifyOp NOTIFY_OP = NOTIFY_OP_REQUEST_LOCK;
static const bool CHECK_FOR_REFRESH = true;
static const bool CHECK_FOR_REFRESH = false;
ClientId client_id;
bool force = false;