-
Notifications
You must be signed in to change notification settings - Fork 69
Open
Labels
bugSomething isn't workingSomething isn't working
Description
I tried to build an image with a systemd Unified Kernel Image as the payload but the build asserts:
assertion failed: data <= 0xffffff
stack backtrace:
0: rust_begin_unwind
at /rustc/2a3e63551fe21458637480a97b65a2d15dec8062/library/std/src/panicking.rs:645:5
1: core::panicking::panic_fmt
at /rustc/2a3e63551fe21458637480a97b65a2d15dec8062/library/core/src/panicking.rs:72:14
2: core::panicking::panic
at /rustc/2a3e63551fe21458637480a97b65a2d15dec8062/library/core/src/panicking.rs:144:5
3: td_shim::write_u24
at ./td-shim/src/lib.rs:105:5
4: td_shim_tools::linker::FvHeaderByte::build_tdx_payload_fv_header
at ./td-shim-tools/src/linker.rs:119:9
5: td_shim_tools::linker::TdShimLinker::build
at ./td-shim-tools/src/linker.rs:367:34
6: td_shim_ld::main
at ./td-shim-tools/src/bin/td-shim-ld/main.rs:93:5
7: core::ops::function::FnOnce::call_once
at /rustc/2a3e63551fe21458637480a97b65a2d15dec8062/library/core/src/ops/function.rs:250:5
AFAIUI, the spec does not limit the size but says (for firmware files section): "If the section size is 0xFFFFFF then the size is defined by a 32-bit integer that follows the 32-bit section header.". Would it make sense to support this 'extended length' approach?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working