diff options
| author | Sunitha Harish <sunithaharish04@gmail.com> | 2022-08-08 11:12:15 +0300 |
|---|---|---|
| committer | Sunitha Harish <sunithaharish04@gmail.com> | 2022-08-11 06:18:26 +0300 |
| commit | 41bb02bb7fad02616066ea6be732a7503741c91a (patch) | |
| tree | 85dc50750ea0abf7edf75c95a081f056941b957a /include/ibm | |
| parent | 2c98676dca920b736b937ad33004bc05b75a450d (diff) | |
| download | bmcweb-41bb02bb7fad02616066ea6be732a7503741c91a.tar.xz | |
IBM Mgmt console writeLock conflict fix
The isConflictRecord method was returning false by default which is
causing ignoring the same resourceId conflicts.
Same resourceId case will pass all the conditions and reach to the end
of the function. Returning true means that there is a conflict.
This commit fixes this by returning true by default
Tested by:
1. Send writeLock requests with same resourceId and segment length
Signed-off-by: Sunitha Harish <sunithaharish04@gmail.com>
Change-Id: Ie65c6394988a357a8c811b621e113c14924bb8f6
Diffstat (limited to 'include/ibm')
| -rw-r--r-- | include/ibm/locks.hpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/ibm/locks.hpp b/include/ibm/locks.hpp index 5df3daa975..5220a5da14 100644 --- a/include/ibm/locks.hpp +++ b/include/ibm/locks.hpp @@ -620,7 +620,7 @@ inline bool Lock::isConflictRecord(const LockRequest& refLockRecord1, ++i; } - return false; + return true; } inline uint32_t Lock::generateTransactionId() |