| Message ID | 20200916162131.22478-4-erichte@linux.ibm.com |
|---|---|
| State | Accepted |
| Headers | show |
| Series | Add initial secure variable storage and backend drivers | expand |
| Context | Check | Description |
|---|---|---|
| snowpatch_ozlabs/apply_patch | success | Successfully applied on branch master (d362ae4f4c521a7faffb1befe2fbba467f2c4d18) |
| snowpatch_ozlabs/snowpatch_job_snowpatch-skiboot | success | Test snowpatch/job/snowpatch-skiboot on branch master |
| snowpatch_ozlabs/snowpatch_job_snowpatch-skiboot-dco | success | Signed-off-by present |
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; };
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> --- include/secvar.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)