On Thu, Nov 6, 2025 at 8:14 AM Andrew Morton <[email protected]> wrote: > > On Wed, 5 Nov 2025 21:09:22 +0800 Pingfan Liu <[email protected]> wrote: > > > When I tested kexec with the latest kernel, I ran into the following > > warning: > > > > [ 40.712410] ------------[ cut here ]------------ > > [ 40.712576] WARNING: CPU: 2 PID: 1562 at kernel/kexec_core.c:1001 > > kimage_map_segment+0x144/0x198 > > [...] > > [ 40.816047] Call trace: > > [ 40.818498] kimage_map_segment+0x144/0x198 (P) > > [ 40.823221] ima_kexec_post_load+0x58/0xc0 > > [ 40.827246] __do_sys_kexec_file_load+0x29c/0x368 > > [...] > > [ 40.855423] ---[ end trace 0000000000000000 ]--- > > > > This is caused by the fact that kexec allocates the destination directly > > in the CMA area. In that case, the CMA kernel address should be exported > > directly to the IMA component, instead of using the vmalloc'd address. > > This is something we should backport into tearlier kernels. > > > Signed-off-by: Pingfan Liu <[email protected]> > > Cc: Andrew Morton <[email protected]> > > Cc: Baoquan He <[email protected]> > > Cc: Alexander Graf <[email protected]> > > Cc: Steven Chen <[email protected]> > > Cc: [email protected] > > To: [email protected] > > So I'm thinking we should add > > Fixes: 0091d9241ea2 ("kexec: define functions to map and unmap segments") > Cc: <[email protected]> > > yes? >
Yes, it should be. Thanks for your help! Best Regards, Pingfan
