aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorMichael Neuling <mikey@neuling.org>2019-05-13 17:09:39 +1000
committerStewart Smith <stewart@linux.ibm.com>2019-05-15 15:43:19 +1000
commit5beda3c6fe5b72aac95b4c13746ae598dfd64c01 (patch)
tree9f8db43611af7bf743c4a70c6843fb5e614be400 /include
parentc8b5e8a95caf029ffe73ea18769fdd7f2da48ab4 (diff)
downloadskiboot-5beda3c6fe5b72aac95b4c13746ae598dfd64c01.zip
skiboot-5beda3c6fe5b72aac95b4c13746ae598dfd64c01.tar.gz
skiboot-5beda3c6fe5b72aac95b4c13746ae598dfd64c01.tar.bz2
nvram: Flag dangerous NVRAM options
Most nvram options used by skiboot are just for debug or testing for regressions. They should never be used long term. We've hit a number of issues in testing and the field where nvram options have been set "temporarily" but haven't been properly cleared after, resulting in crashes or real bugs being masked. This patch marks most nvram options used by skiboot as dangerous and prints a chicken to remind users of the problem. Signed-off-by: Michael Neuling <mikey@neuling.org> Reviewed-by: Samuel Mendoza-Jonas <sam@mendozajonas.com> Acked-By: Alistair Popple <alistair@popple.id.au> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
Diffstat (limited to 'include')
-rw-r--r--include/nvram.h6
1 files changed, 4 insertions, 2 deletions
diff --git a/include/nvram.h b/include/nvram.h
index 012c107..a018a11 100644
--- a/include/nvram.h
+++ b/include/nvram.h
@@ -24,7 +24,9 @@ bool nvram_validate(void);
bool nvram_has_loaded(void);
bool nvram_wait_for_load(void);
-const char *nvram_query(const char *name);
-bool nvram_query_eq(const char *key, const char *value);
+const char *nvram_query_safe(const char *name);
+const char *nvram_query_dangerous(const char *name);
+bool nvram_query_eq_safe(const char *key, const char *value);
+bool nvram_query_eq_dangerous(const char *key, const char *value);
#endif /* __NVRAM_H */