prepareForS3Sleep: use locking range

Untested, but it seems odd to use 0 when it's passed in from the command line.
UtilFunction · Jun 6, 2019 · da7b267 · da7b267
1 parent c1689c7
commit da7b267
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/linux/DtaDevLinuxDrive.cpp b/linux/DtaDevLinuxDrive.cpp
@@ -30,7 +30,7 @@ uint8_t DtaDevLinuxDrive::prepareForS3Sleep(uint8_t lockingrange, const char *us
 
     opal_lock_unlock opal_ioctl_data={};
     opal_ioctl_data.l_state = OPAL_RW;
-    opal_ioctl_data.session.opal_key.lr = 0;
+    opal_ioctl_data.session.opal_key.lr = lockingrange;
 
     if (!strcmp("Admin1", userid))
     {

diff --git a/linux/DtaDevOS.cpp b/linux/DtaDevOS.cpp
@@ -195,7 +195,7 @@ uint8_t DtaDevOS::prepareForS3Sleep(uint8_t lockingrange, const char* userid, ch
     DtaHashPwd(hash, password, this);
     hash->erase(hash->begin(), hash->begin()+2);
 
-    err = drive->prepareForS3Sleep(0, userid, hash);
+    err = drive->prepareForS3Sleep(lockingrange, userid, hash);
     if (err)
     {
         LOG(E) << "Error saving the password to  the kernel errno = " << errno;