commit 3432a0ace7ef0ea1d6478cdf3d5e95f6c982da30
author PavanKumarIntel <pavanx.kumar.martha@intel.com> Mon Jul 10 14:37:29 2023 +0000
committer AppaRao Puli <apparao.puli@intel.com> Tue Jul 18 14:59:05 2023 +0000
tree 3d5a30f44550eb38676d08490ff2ab4f57a60f7c
parent ac330b8e705c53a2df9395bbf37f360dbc7e49cc

Fix to prevent the FRU corruption while updating

While updating the FRU , if we try to read the FRU data
by running command "ipmitool fru list" before 2 seconds after
editing the FRU, getting corrupted data

Tested:

    FRU data not corrupted and updated successfully

Change-Id: I8d2949706378b776888c6768755a57f3727ffb51
Signed-off-by: PavanKumarIntel <pavanx.kumar.martha@intel.com>

src/storagecommands.cpp

diff --git a/src/storagecommands.cpp b/src/storagecommands.cpp
index 2554174..67ca8d8 100644
--- a/src/storagecommands.cpp
+++ b/src/storagecommands.cpp
@@ -309,6 +309,12 @@
         return IPMI_CC_SENSOR_INVALID;
     }
 
+    if (writeTimer->isRunning())
+    {
+        phosphor::logging::log<phosphor::logging::level::ERR>(
+            "Couldn't get raw fru as fru is updating");
+        return ipmi::ccBusy;
+    }
     fruCache.clear();
 
     cacheBus = deviceFind->second.first;