Skip to content

v4.4.1
Compare
Choose a tag to compare
@github-actions github-actions released this 06 Sep 19:40
· 314 commits to refs/heads/main since this release
v4.4.1
0847402
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

  • Remove Unused Environment Variables @os-d (#695)
    Change Details
      ## Description

    There are several errors produced when building QemuQ35Pkg and QemuSbsaPkg indicating that some relative paths cannot be converted to absolute paths. This is because these paths do not exist in the code tree anymore.

    This patch removes the unused env vars.

    For each item, place an "x" in between [ and ] if true. Example: [x].
    (you can also check items in the GitHub UI)

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    Still builds without these.

    Integration Instructions

    N/A.



🐛 Bug Fixes

  • QemuQ35Pkg/SmmAccess: Add missing include guard @makubacki (#691)
    Change Details
      ## Description

    All header files should have include guards.

    See the following for more info:
    https://codeql.github.com/codeql-query-help/cpp/cpp-missing-header-guard/

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    • CI build
    • Ran CodeQL with cpp-missing-header-guard enabled

    Integration Instructions

    N/A



  • QemuRunner: Prevent virtual drive unknown image format warning @makubacki (#686)
    Change Details
      ## Description

    The virtual drive image is passed with the following parameter:

    -hdd <VirtualDrivePath>

    This results in the following warning:

    WARNING: Image format was not specified for 'VirtualDrive.img' and
         probing guessed raw.

         Automatically detecting the format is dangerous for raw
         images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the
         restrictions.

    This passes the image using -drive to resolve the warning.

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    • QemuQ35Pkg and QemuSbsaPkg build and run

    Integration Instructions

    N/A



🔐 Security Impacting

  • Remove physical presence from Q35 and SBSA @TaylorBeebe (#687)
    Change Details
      ## Description

    The physical presence check is a poor way to determine if a user is actually physically present at the machine. Because some security checks can be bypassed with physical presence, set physical presence to FALSE.

    • Impacts functionality?
      • Functionality - Does the change ultimately impact how firmware functions?
      • Examples: Add a new library, publish a new PPI, update an algorithm, ...
    • Impacts security?
      • Security - Does the change have a direct security impact on an application,
        flow, or firmware?
      • Examples: Crypto algorithm change, buffer overflow fix, parameter
        validation improvement, ...
    • Breaking change?
      • Breaking change - Will anyone consuming this change experience a break
        in build or boot behavior?
      • Examples: Add a new library class, move a module to a different repo, call
        a function in a new library class in a pre-existing module, ...
    • Includes tests?
      • Tests - Does the change include any explicit test code?
      • Examples: Unit tests, integration tests, robot tests, ...
    • Includes documentation?
      • Documentation - Does the change contain explicit documentation additions
        outside direct code modifications (and comments)?
      • Examples: Update readme file, add feature readme file, link to documentation
        on an a separate Web page, ...

    How This Was Tested

    Tested on Q35 and SBSA

    Integration Instructions

    N/A



🛠️ Submodule Updates

  • Bump Features/CONFIG from 1.0.1 to 2.0.0 @ProjectMuBot (#694)
    Change Details
      Bumps Features/CONFIG from `1.0.1` to `2.0.0`

    Introduces 12 new commits in Features/CONFIG.

    Commits
    • c608e2 Repo File Sync: Update to Mu DevOps 5.0.6 and Ubuntu container 3bf70b5 (#222)
    • a8adde pip: bump edk2-pytool-extensions from 0.23.9 to 0.23.10 (#223)
    • 861ed2 pip: bump xmlschema from 2.3.1 to 2.4.0 (#225)
    • a78277 SetupDataPkg/Tools/KnobService.py: Fix flake8 6.1.0 error
    • 34e9b7 pip: bump flake8 from 6.0.0 to 6.1.0
    • 5e9478 pip: bump edk2-pytool-library from 0.15.3 to 0.16.1 (#227)
    • 523836 pip: bump regex from 2023.6.3 to 2023.8.8 (#226)
    • 2d26e7 pip: bump edk2-pytool-library from 0.16.1 to 0.17.0 (#228)
    • 06377f pip: bump edk2-pytool-extensions from 0.23.10 to 0.24.0 (#229)
    • 51ce03 UpdateConfigHdr.py: Resolve mws deprecation (#231)
    • 0613e8 Repo File Sync: Update to Mu DevOps v6.1.0 (#230)
    • 684684 Repo File Sync: Add extra_cargo_steps parameter to MuDevOpsWrapper.yml (#232)

    Signed-off-by: Project Mu Bot mubot@microsoft.com



  • Bump MU\_BASECORE from 2023020005.0.1 to 2023020006.0.0 @ProjectMuBot (#693)
    Change Details
      Bumps MU_BASECORE from `2023020005.0.1` to `2023020006.0.0`

    Introduces 4 new commits in MU_BASECORE.

    Commits
    • de9f9a [CHERRY-PICK] UefiCpuLib: Remove UefiCpuLib.
    • 6e954f PcAtChipsetPkg: Remove UefiCpuLib reference
    • 2d6b31 Repo File Sync: Add extra_cargo_steps parameter to MuDevOpsWrapper.yml (#547)
    • 549888 OverrideValidation: bugfix handling file missing from workspace (#549)

    Signed-off-by: Project Mu Bot mubot@microsoft.com



Full Changelog: v4.4.0...v4.4.1

Contributors

makubacki, os-d, and 2 other contributors
Assets 7
Loading