arm64: EFI stub isolation
Get series with b4
b4 am [email protected]Versions newest first
- v4 Latest3 patches 0 repliesNew
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | arm64/efi: remove /chosen/linux,uefi-stub-kern-ver DT property | +0 | 0 replies | |
| 3/3 | arm64/efi: isolate EFI stub from the kernel proper | +0 | 0 replies | |
| 3/3 | arm64/efi: isolate EFI stub from the kernel proper | +0 | 0 replies |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Matt Fleming |
|---|---|
| 1/3 | R-b |
| 3/3 | R-b R-b |
| 3/3 | R-b R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v4 0/3] arm64: EFI stub isolation
Quoted 7 lines · Ard Biesheuvel
We need to ensure that the EFI stub only uses parts of the kernel proper that are safe to use when the kernel virtual mapping is not active yet.
So move all C code dependencies to the libstub, which is built with all instrumentation (gcov, kasan) disabled, and do a verification pass to ensure that no absolute relocations are used.
Quoted 5 lines
On the arm64 side, annotate all the stub's dependencies as safe for PI (position independent
@Matt: if you are OK with these, may we please have your ack on patches #1 and #2 so that Catalin can pick up the series? Thanks.
I assumed you meant PATCH 1 and PATCH 3. If so, yeah, these look fine to be taken through Catalin's tree.
Signature · 1 line
Matt Fleming, Intel Open Source Technology Center