<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Tianocore/edk2.git/EmbeddedPkg, branch dependabot/github_actions/github/codeql-action-4.39.3</title>
<subtitle>EDK II (mirror)</subtitle>
<id>https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Fgithub%2Fcodeql-action-4.39.3</id>
<link rel='self' href='https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Fgithub%2Fcodeql-action-4.39.3'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/'/>
<updated>2026-11-02T03:24:56+00:00</updated>
<entry>
<title>EmbeddedPkg/PrePiLib: drop DstBuffer adjustment in FfsProcessSection</title>
<updated>2026-11-02T03:24:56+00:00</updated>
<author>
<name>Ming Huang</name>
<email>huangming@linux.alibaba.com</email>
</author>
<published>2026-10-23T04:05:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=496fd85f26d40871c97c5835bf5ed849b6eb8a70'/>
<id>urn:sha1:496fd85f26d40871c97c5835bf5ed849b6eb8a70</id>
<content type='text'>
The DstBuffer adjustment in FfsProcessSection() was added in the
BeagleBoard era (2ef2b01e07), when the decompressed section stream
placed the encapsulated section data directly after the 4/8 byte
EFI_COMMON_SECTION_HEADER. Bumping DstBuffer forward by
EFI_PAGE_SIZE - sizeof (EFI_COMMON_SECTION_HEADER) put the section
data back on a page boundary at the cost of one extra page.

For FV images this compensation is obsolete and harmful:

- GenFds aligns the FV_IMAGE section data inside the stream to the
  FvAlignment recorded in the inner FV header, by emitting a RAW pad
  section in front of the FV_IMAGE section. With a page aligned
  DstBuffer, the decompressed FV therefore already starts at a
  FvAlignment-aligned offset (e.g. DstBuffer + 0x10 for a typical
  FvAlignment = 16 build).

- The forward bump instead moves the FV to
  DstBuffer + EFI_PAGE_SIZE - sizeof (EFI_COMMON_SECTION_HEADER) + pad,
  which is 12 bytes off for FvAlignment = 16. FfsProcessFvFile() then
  takes its misalignment fallback and AllocateAlignedPages() a second
  buffer to CopyMem() the entire FV, doubling the temporary RAM
  footprint of the decompressed DXEFV.

On platforms with a modest SEC temporary RAM pool this is fatal: a
RISC-V platform with a 16 MiB pool and a ~9 MiB LZMA compressed DXEFV
fails to boot with EFI_OUT_OF_RESOURCES from DecompressFirstFv(),
because the redundant aligned copy no longer fits. The same FDF
pattern (FvAlignment = 16 DXEFV wrapped in the LZMA GUIDED section)
is used by OvmfPkg/RiscVVirt, which gets away with it only because
of its more generous memory layout, and pays a full extra copy of
the FV on every boot.

Remove the adjustment, and the extra page that was reserved for it,
so the decompressed FV keeps its natural, build-time guaranteed
alignment. Verified on the affected RISC-V platform: the FV now
lands 16-byte aligned, the fallback copy is not taken, and boot
succeeds in both RELEASE and DEBUG builds.

Cc: Leif Lindholm &lt;leif.lindholm@oss.qualcomm.com&gt;
Cc: Ard Biesheuvel &lt;ardb+tianocore@kernel.org&gt;
Cc: Abner Chang &lt;abner.chang@amd.com&gt;
Signed-off-by: Ming Huang &lt;huangming@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg/MmcDxe: Fix MmcIoBlocks() when MultiBlock() is not supported</title>
<updated>2026-10-29T11:12:38+00:00</updated>
<author>
<name>Pierre Gondois</name>
<email>pierre.gondois@arm.com</email>
</author>
<published>2026-08-12T14:53:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=58ad5f876c99fd268d01a673efb8f1106d9458b9'/>
<id>urn:sha1:58ad5f876c99fd268d01a673efb8f1106d9458b9</id>
<content type='text'>
BlockCount is used as both:
- maximum number of blocks possible to access
- number of blocks accessed in the current loop iteration
If MultiBlock() is not supported, accessing more than 1 block
can lead to BlockCount=0 and an infinite loop.

Rationalize the variables as:
- MaxBlock: maximum number of blocks to access
- BlockCount: number of blocks accessed in the current loop iteration

Signed-off-by: Pierre Gondois &lt;pierre.gondois@arm.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: Add BuildResourceDescriptor2Hob to HobLibs</title>
<updated>2026-10-22T23:28:02+00:00</updated>
<author>
<name>Aaron Pop</name>
<email>aaronpop@microsoft.com</email>
</author>
<published>2026-07-28T21:01:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=43965090e5dc83f298cdff31b6ebb34f0f931e13'/>
<id>urn:sha1:43965090e5dc83f298cdff31b6ebb34f0f931e13</id>
<content type='text'>
Add BuildResourceDescriptor2Hob to HobLib implementations
as described in PI 1.10 specification.

Signed-off-by: Aaron Pop &lt;aaronpop@microsoft.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg/PrePiHobLib: Reject oversized GUID HOB payloads</title>
<updated>2026-10-19T04:26:39+00:00</updated>
<author>
<name>Stanislaw Grams</name>
<email>stanislaw.grams@intel.com</email>
</author>
<published>2026-10-09T11:38:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=0b14d8c58c8379d25fde73e2a64dd16c5d1c7062'/>
<id>urn:sha1:0b14d8c58c8379d25fde73e2a64dd16c5d1c7062</id>
<content type='text'>
Check the GUID HOB payload length before the UINT16 allocation cast.
Use the aligned maximum total HOB length of 0xFFF8 instead of 0xFFFF
in both the assertion and runtime guard.

Return NULL for oversized requests when assertions are disabled or
return, and document the allocation and copy-wrapper failure behavior.

Signed-off-by: Stanislaw Grams &lt;stanislaw.grams@intel.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: Resolve ReportStatusCodeLib library class</title>
<updated>2026-10-07T16:10:21+00:00</updated>
<author>
<name>Khalid Ali</name>
<email>khaliidcaliy@gmail.com</email>
</author>
<published>2026-10-06T08:38:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=21744e8b5c02f271b5103abfcab3d6b6e6bf7a4e'/>
<id>urn:sha1:21744e8b5c02f271b5103abfcab3d6b6e6bf7a4e</id>
<content type='text'>
The ReportStatusCodeLib library class references  a library instance
that doesn't support that class. This makes the build to throw a warning
about it.

This change resolves ReportStatusCodeLib into one of the supported
instances. There are 2 instances support that class which are DxeReportStatusCodeLib
and PeiReportStatusCodeLib.

Signed-off-by: Khalid Ali &lt;khaliidcaliy@gmail.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: MmcIoBlocks: Fix logical error in timeout</title>
<updated>2026-09-04T01:50:12+00:00</updated>
<author>
<name>snowpiaoling</name>
<email>1972997989@qq.com</email>
</author>
<published>2026-08-07T04:28:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=33ce6ba36d40f6a89cf8a0dc55ff358b938bda6d'/>
<id>urn:sha1:33ce6ba36d40f6a89cf8a0dc55ff358b938bda6d</id>
<content type='text'>
In eMMC status detection logic in the `MmcIoBlocks' function, if a timeout
occurs, the Timeout variable will end with a value -1 as the self-
subtraction operation is performed after determining 0 in the while loop.
This means that the function could never return a `EFI_NOT_READY' status.

As Timeout is of a signed type, change the conditional statement to
less-than-or-equal to 0 to fix timeout/busy detection.

Signed-off-by: snowpiaoling &lt;1972997989@qq.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: MmcTransferBlock: Add Timeout Handle</title>
<updated>2026-09-03T14:08:04+00:00</updated>
<author>
<name>snowpiaoling</name>
<email>1972997989@qq.com</email>
</author>
<published>2026-08-30T01:28:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=65f06e62d5de8f9e4cbbc8735d0f6f15a721b169'/>
<id>urn:sha1:65f06e62d5de8f9e4cbbc8735d0f6f15a721b169</id>
<content type='text'>
In the `MmcTransferBlock' function, the `Timeout' variable is defined but not
processed, so timeout handling is added.

Signed-off-by: snowpiaoling &lt;1972997989@qq.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: PrePiHobLib: Don't Duplicate Stack Hob Mem Alloc</title>
<updated>2026-09-03T09:00:37+00:00</updated>
<author>
<name>Oliver Smith-Denny</name>
<email>osde@microsoft.com</email>
</author>
<published>2026-09-02T19:48:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=e9b31236bdbc6e0fe179c56d16c6ffe125c6069d'/>
<id>urn:sha1:e9b31236bdbc6e0fe179c56d16c6ffe125c6069d</id>
<content type='text'>
Currently, PrePiHobLib will produce two memory allocation
HOBs for the stack, based on the behavior it copied from
DxeIpl. This is an incorrect description of handoff state.

This commit follows the DxeIpl logic change to only produce
a single memory allocation HOB for the new stack. The
difference is that PrePiHobLib does not preserve the old
stack region and instead frees it. That behavior is
preserved.

Signed-off-by: Oliver Smith-Denny &lt;osde@microsoft.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg: normalize mmc interaction latency to 1us</title>
<updated>2026-08-30T01:48:20+00:00</updated>
<author>
<name>snowpiaoling</name>
<email>1972997989@qq.com</email>
</author>
<published>2026-08-07T04:30:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=15a434a2bdac898e68d21cd659969abcadec37cb'/>
<id>urn:sha1:15a434a2bdac898e68d21cd659969abcadec37cb</id>
<content type='text'>
Upon inspecting the source code, I found that the original implementation
of eMMC timeout in MmcDxe is affected by the CPU execution speed. With
higher-performance CPUs, the actual timeout duration would be shortened as
it was not based on wall clock.

Add a precise 1us delay to each iteration of the wait loop to make the
actual duration of the delay clock- and performance-agnostic.

Signed-off-by: snowpiaoling &lt;1972997989@qq.com&gt;
</content>
</entry>
<entry>
<title>EmbeddedPkg/AcpiLib: Fix memory corruption in AcpiAmlObjectUpdateInteger</title>
<updated>2026-08-12T08:13:56+00:00</updated>
<author>
<name>Johnny.Fan</name>
<email>Johnny.Fan@cixtech.com</email>
</author>
<published>2026-07-07T09:11:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=2970e5699ba6267f3384ffab20f96647578aebc8'/>
<id>urn:sha1:2970e5699ba6267f3384ffab20f96647578aebc8</id>
<content type='text'>
  The original implementation of AcpiAmlObjectUpdateInteger had a critical
  bug when updating integer objects that were encoded with AML_ZERO_OP(0x00)
  or AML_ONE_OP(0x01), which are 1-byte optimized encodings.

  When the caller tried to update such an object to a value other than 0
  or 1, the code would:
  1. Overwrite the opcode byte with the new value's LSB
  2. This changed the opcode itself, e.g. 0x0B becomes AML_WORD_PREFIX
  3. Subsequent AML bytes (name segments of following objects) get
     misinterpreted as integer data
  4. Result: silent AML structure is silently corrupted, causing the OS to
     fail parsing ACPI tables and eventually crash.

  The fix:
  1. Only allow 0 -&gt; 0 or 1 updates using the original 1-byte encoding
  2. For any other value, explicitly fail with a diagnostic
  3. Provide clear debug instructions on how to fix the ASL source

Reviewed-by: jie.fu &lt;jie.fu@cixtech.com&gt;
Signed-off-by: Johnny.Fan &lt;Johnny.Fan@cixtech.com&gt;
</content>
</entry>
</feed>
