diff options
author | James Morse <james.morse@arm.com> | 2019-01-29 18:48:42 +0000 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-02-07 23:10:45 +0100 |
commit | eeb2555779471abdbcc6289a52dc54ce513feaf2 (patch) | |
tree | e2754b4d4c6709020b2c5a1d1d2f77dabeeec91b /include | |
parent | fb7be08f1a091ec243780bfdad4bf0c492057808 (diff) | |
download | linux-stable-eeb2555779471abdbcc6289a52dc54ce513feaf2.tar.gz linux-stable-eeb2555779471abdbcc6289a52dc54ce513feaf2.tar.bz2 linux-stable-eeb2555779471abdbcc6289a52dc54ce513feaf2.zip |
ACPI / APEI: Don't store CPER records physical address in struct ghes
When CPER records are found the address of the records is stashed
in the struct ghes. Once the records have been processed, this
address is overwritten with zero so that it won't be processed
again without being re-populated by firmware.
This goes wrong if a struct ghes can be processed concurrently,
as can happen at probe time when an NMI occurs. If the NMI arrives
on another CPU, the probing CPU may call ghes_clear_estatus() on the
records before the handler had finished with them.
Even on the same CPU, once the interrupted handler is resumed, it
will call ghes_clear_estatus() on the NMIs records, this memory may
have already been re-used by firmware.
Avoid this stashing by letting the caller hold the address. A
later patch will do away with the use of ghes->flags in the
read/clear code too.
Signed-off-by: James Morse <james.morse@arm.com>
Reviewed-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include')
-rw-r--r-- | include/acpi/ghes.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/acpi/ghes.h b/include/acpi/ghes.h index cd9ee507d860..f82f4a7ddd90 100644 --- a/include/acpi/ghes.h +++ b/include/acpi/ghes.h @@ -22,7 +22,6 @@ struct ghes { struct acpi_hest_generic_v2 *generic_v2; }; struct acpi_hest_generic_status *estatus; - u64 buffer_paddr; unsigned long flags; union { struct list_head list; |