diff options
author | Matthew Garrett <matthewgarrett@google.com> | 2019-06-07 13:51:47 -0700 |
---|---|---|
committer | Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> | 2019-06-24 23:57:50 +0300 |
commit | 166a2809d65b282272c474835ec22c882a39ca1b (patch) | |
tree | 3ad4681aa56962a7834f8ad6c8a45d1ec73e3c59 /CREDITS | |
parent | 82d736ac56d7cd78696c5234853684bad05efadf (diff) | |
download | linux-166a2809d65b282272c474835ec22c882a39ca1b.tar.gz linux-166a2809d65b282272c474835ec22c882a39ca1b.tar.bz2 linux-166a2809d65b282272c474835ec22c882a39ca1b.zip |
tpm: Don't duplicate events from the final event log in the TCG2 log
After the first call to GetEventLog() on UEFI systems using the TCG2
crypto agile log format, any further log events (other than those
triggered by ExitBootServices()) will be logged in both the main log and
also in the Final Events Log. While the kernel only calls GetEventLog()
immediately before ExitBootServices(), we can't control whether earlier
parts of the boot process have done so. This will result in log entries
that exist in both logs, and so the current approach of simply appending
the Final Event Log to the main log will result in events being
duplicated.
We can avoid this problem by looking at the size of the Final Event Log
just before we call ExitBootServices() and exporting this to the main
kernel. The kernel can then skip over all events that occured before
ExitBootServices() and only append events that were not also logged to
the main log.
Signed-off-by: Matthew Garrett <mjg59@google.com>
Reported-by: Joe Richey <joerichey@google.com>
Suggested-by: Joe Richey <joerichey@google.com>
Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions