v2023020001.1.0

What's Changed

🚀 Features & ✨ Enhancements

• Close ReadyToBoot and ExitBootServices events if a reset is notified. @joschock (#275)
  
  Change Details

    ## Description

  Close the ReadyToBoot and ExitBootServices events in the reset notification. This prevents the file logger from trying to access the file system after its reset notification has run in the event that the platform implementation invokes one of those notifications in the reset path (which it shouldn't, but some do).

  • Impacts functionality?
    • Should not impact functionality since the reset notification is expected to be the last point at which file log can be flushed on most architectures.
  • Impacts security?
    • No security impact
  • Breaking change?
    • Not breaking change.
  • Includes tests?
    • No tests included as no new functionality is introduced.
  • Includes documentation?
    • No docs changed as no new functionality is introduced.

  How This Was Tested

  Executed reset, confirmed that file log is flushed as expected. On a system that also invokes the exit boot services notification in the reset path, confirmed that log file is not flushed in the exit boot services notification. Confirmed that on normal boot path to OS, log flush is executed in the exit boot path notification.

  Integration Instructions

  N/A

    </blockquote>
    <hr>
  </details>
  

Full Changelog: v2023020001.0.1...v2023020001.1.0