When booting a new kernel with kexec_file, the kernel picks a target
location that the kernel should live at, then allocates random pages,
checks whether any of those patches magically happens to coincide with
a target address range and if so, uses them for that range.
For every page allocated thi
On 5/13/2025 4:41 AM, Mimi Zohar wrote:
Hi Steven,
On Fri, 2025-05-02 at 13:03 -0700, steven chen wrote:
From: Steven Chen
Kdump kernel doesn't need IMA to do integrity measurement.
Hence the measurement list in 1st kernel doesn't need to be copied to
kdump kenrel.
^kernel
Please use "scrip
On 5/12/2025 7:25 PM, Baoquan He wrote:
On 05/02/25 at 01:03pm, steven chen wrote:
From: Steven Chen
Kdump kernel doesn't need IMA to do integrity measurement.
Hence the measurement list in 1st kernel doesn't need to be copied to
kdump kenrel.
Here skip allocating buffer for measurement list
From: Steven Chen
Kdump kernel doesn't need IMA to do integrity measurement.
Hence the measurement list in 1st kernel doesn't need to be copied to
kdump kernel.
Here skip allocating buffer for measurement list copying if loading
kdump kernel. Then there won't be the later handling related to
ima
On 5/7/2025 3:12 PM, Borislav Petkov wrote:
On Tue, May 06, 2025 at 06:35:29PM +, Ashish Kalra wrote:
From: Ashish Kalra
When the shared pages are being made private during kdump preparation
there are additional checks to handle shared GHCB pages.
These additional checks include handling
Hi Steven,
On Fri, 2025-05-02 at 13:03 -0700, steven chen wrote:
> From: Steven Chen
>
> Kdump kernel doesn't need IMA to do integrity measurement.
> Hence the measurement list in 1st kernel doesn't need to be copied to
> kdump kenrel.
^kernel
Please use "scripts/checkpatch.pl --codespell" to
If a buildroot enviorment does not provide libzstd and kexec_file_load a
zstd compressed kernel, it will suffer from coredump.
The following is observed from the coredump
Core was generated by `/sbin/kexec -s -p
--command-line=BOOT_IMAGE=\(hd0,gpt2\)/vmlinuz-6.15.0-0.rc5.250509g9c69f8884904.47.f
When booting a new kernel with kexec_file, the kernel picks a target
location that the kernel should live at, then allocates random pages,
checks whether any of those patches magically happens to coincide with
a target address range and if so, uses them for that range.
For every page allocated thi
Hi Andrew,
On 13.05.25 01:59, Andrew Morton wrote:
On Mon, 12 May 2025 22:57:52 + Alexander Graf wrote:
When booting a new kernel with kexec_file, the kernel picks a target
location that the kernel should live at, then allocates random pages,
checks whether any of those patches magically
