Re: [PATCH v2 1/1] kexec_core: Accept unaccepted kexec segments' destination addresses

2025-02-19 Thread Dave Hansen
On 12/13/24 01:54, Yan Zhao wrote: > Accept the destination addresses during the kexec load, immediately after > they pass sanity checks. This ensures the code is located in a common place > shared by both the kexec_load and kexec_file_load system calls. So, we've got an end-user-visible bug. Eric

Re: [PATCH v2 1/1] kexec_core: Accept unaccepted kexec segments' destination addresses

2025-02-14 Thread Kirill A. Shutemov
On Thu, Feb 13, 2025 at 07:50:42AM -0800, Dave Hansen wrote: > On 12/13/24 01:54, Yan Zhao wrote: > > + /* > > +* The destination addresses are searched from system RAM rather than > > +* being allocated from the buddy allocator, so they are not guaranteed > > +* to be accepted by the

Re: [PATCH v2 1/1] kexec_core: Accept unaccepted kexec segments' destination addresses

2025-02-13 Thread Dave Hansen
On 12/13/24 01:54, Yan Zhao wrote: > + /* > + * The destination addresses are searched from system RAM rather than > + * being allocated from the buddy allocator, so they are not guaranteed > + * to be accepted by the current kernel. Accept the destination > + * addresses b

[PATCH v2 1/1] kexec_core: Accept unaccepted kexec segments' destination addresses

2024-12-13 Thread Yan Zhao
In TDX, to run a linux guest, TDs (hardware-isolated VMs) must accept before accessing private memory. Accessing private memory before acceptance is considered a fatal error and may result in the termination of the TD. The "accepting memory" operation in guest includes the following steps: - trigg