Searched hist:"7684 bd334d9d4ca4f09873e88d9c0131a2cf6c3b" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/include/linux/ |
| H A D | pstore_ram.h | diff 7684bd334d9d4ca4f09873e88d9c0131a2cf6c3b Tue Oct 30 02:52:34 CDT 2018 Peng Wang <wangpeng15@xiaomi.com> pstore: Avoid duplicate call of persistent_ram_zap()
When initialing a prz, if invalid data is found (no PERSISTENT_RAM_SIG),
the function call path looks like this:
ramoops_init_prz ->
persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
persistent_ram_zap
As we can see, persistent_ram_zap() is called twice.
We can avoid this by adding an option to persistent_ram_new(), and
only call persistent_ram_zap() when it is needed.
Signed-off-by: Peng Wang <wangpeng15@xiaomi.com>
[kees: minor tweak to exit path and commit log]
Signed-off-by: Kees Cook <keescook@chromium.org>
|
| /openbmc/linux/fs/pstore/ |
| H A D | ram_core.c | diff 7684bd334d9d4ca4f09873e88d9c0131a2cf6c3b Tue Oct 30 02:52:34 CDT 2018 Peng Wang <wangpeng15@xiaomi.com> pstore: Avoid duplicate call of persistent_ram_zap()
When initialing a prz, if invalid data is found (no PERSISTENT_RAM_SIG),
the function call path looks like this:
ramoops_init_prz ->
persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
persistent_ram_zap
As we can see, persistent_ram_zap() is called twice.
We can avoid this by adding an option to persistent_ram_new(), and
only call persistent_ram_zap() when it is needed.
Signed-off-by: Peng Wang <wangpeng15@xiaomi.com>
[kees: minor tweak to exit path and commit log]
Signed-off-by: Kees Cook <keescook@chromium.org>
|
| H A D | ram.c | diff 7684bd334d9d4ca4f09873e88d9c0131a2cf6c3b Tue Oct 30 02:52:34 CDT 2018 Peng Wang <wangpeng15@xiaomi.com> pstore: Avoid duplicate call of persistent_ram_zap()
When initialing a prz, if invalid data is found (no PERSISTENT_RAM_SIG),
the function call path looks like this:
ramoops_init_prz ->
persistent_ram_new -> persistent_ram_post_init -> persistent_ram_zap
persistent_ram_zap
As we can see, persistent_ram_zap() is called twice.
We can avoid this by adding an option to persistent_ram_new(), and
only call persistent_ram_zap() when it is needed.
Signed-off-by: Peng Wang <wangpeng15@xiaomi.com>
[kees: minor tweak to exit path and commit log]
Signed-off-by: Kees Cook <keescook@chromium.org>
|