diff mbox series

[v5,03/20] include/secvar.h: add .lockdown() hook to secvar storage driver

Message ID 20200612202514.15032-4-erichte@linux.ibm.com
State Superseded
Headers show
Series Add initial secure variable storage and backend drivers | expand

Checks

Context Check Description
snowpatch_ozlabs/snowpatch_job_snowpatch-skiboot-dco success Signed-off-by present
snowpatch_ozlabs/snowpatch_job_snowpatch-skiboot success Test snowpatch/job/snowpatch-skiboot on branch master
snowpatch_ozlabs/apply_patch success Successfully applied on branch master (fe70fbb78d33abea788a3221bc409a7c50c019c3)

Commit Message

Eric Richter June 12, 2020, 8:24 p.m. UTC
Previously, it was implied that the storage driver would lock itself after
performing a write action. As this behavior is not particularly clear when
reviewing the main secvar flow, this action instead has been made explicit.

Signed-off-by: Eric Richter <erichte@linux.ibm.com>
---
V5:
 - split this into its own patch
 - squashed in a whitespace fix

 include/secvar.h | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)
diff mbox series

Patch

diff --git a/include/secvar.h b/include/secvar.h
index ec812b85..76525534 100644
--- a/include/secvar.h
+++ b/include/secvar.h
@@ -9,9 +9,10 @@ 
 struct secvar;
 
 struct secvar_storage_driver {
-        int (*load_bank)(struct list_head *bank, int section);
-        int (*write_bank)(struct list_head *bank, int section);
-        int (*store_init)(void);
+	int (*load_bank)(struct list_head *bank, int section);
+	int (*write_bank)(struct list_head *bank, int section);
+	int (*store_init)(void);
+	void (*lockdown)(void);
 	uint64_t max_var_size;
 };