update_engine: Fix TPM variable name max_kernel_rollfoward

- In a previous CL I named the variable incorrectly

BUG=chromium:814090
TEST=FEATURES=test emerge-samus update_engine

Change-Id: I17cbc85d42ba03040bfdae436cedd0238698b47e
Reviewed-on: https://chromium-review.googlesource.com/1059944
Commit-Ready: Zentaro Kavanagh <zentaro@chromium.org>
Tested-by: Zentaro Kavanagh <zentaro@chromium.org>
Reviewed-by: Amin Hassani <ahassani@chromium.org>
diff --git a/common/fake_hardware.h b/common/fake_hardware.h
index 68fdd5b..d699fb7 100644
--- a/common/fake_hardware.h
+++ b/common/fake_hardware.h
@@ -40,7 +40,7 @@
   // Default value for crossystem tpm_fwver.
   static const int kMinFirmwareKeyVersion = 13;
 
-  // Default value for crossystem max_kernel_rollforward. This value is the
+  // Default value for crossystem kernel_max_rollforward. This value is the
   // default for consumer devices and effectively means "unlimited rollforward
   // is allowed", which is the same as the behavior prior to implementing
   // roll forward prevention.
@@ -79,8 +79,8 @@
     return min_firmware_key_version_;
   }
 
-  bool SetMaxKernelKeyRollforward(int max_kernel_rollforward) override {
-    max_kernel_rollforward_ = max_kernel_rollforward;
+  bool SetMaxKernelKeyRollforward(int kernel_max_rollforward) override {
+    kernel_max_rollforward_ = kernel_max_rollforward;
     return true;
   }
 
@@ -167,7 +167,7 @@
   }
 
   // Getters to verify state.
-  int GetMaxKernelKeyRollforward() const { return max_kernel_rollforward_; }
+  int GetMaxKernelKeyRollforward() const { return kernel_max_rollforward_; }
 
  private:
   bool is_official_build_{true};
@@ -182,7 +182,7 @@
   std::string ec_version_{"Fake EC v1.0a"};
   int min_kernel_key_version_{kMinKernelKeyVersion};
   int min_firmware_key_version_{kMinFirmwareKeyVersion};
-  int max_kernel_rollforward_{kMaxKernelRollforward};
+  int kernel_max_rollforward_{kMaxKernelRollforward};
   int powerwash_count_{kPowerwashCountNotSet};
   bool powerwash_scheduled_{false};
   bool first_active_omaha_ping_sent_{false};