Re: [PATCH v3 1/2] kho: add support for preserving vmalloc allocations

On Mon, Sep 08, 2025 at 01:35:27PM +0300, Mike Rapoport wrote: > +static struct kho_vmalloc_chunk *new_vmalloc_chunk(struct kho_vmalloc_chunk > *cur) > +{ > + struct kho_vmalloc_chunk *chunk; > + int err; > + > + chunk = kzalloc(PAGE_SIZE, GFP_KERNEL); > + if (!chunk) > +

Re: [PATCH RFC][makedumpfile 01/10] dwarf_info: Support kernel address randomization

Hi,Liu Thanks your patch. What kind of environment did you test this KASLR problem ? Especialy is it kernel verssion 6.11.8-300.fc41.x86_64 ? Have you checked other versions? Additionally, do you know the version of eppic ? Also, if possible, show this problem results when an error occurs and the

[PATCH v3 1/2] kho: add support for preserving vmalloc allocations

From: "Mike Rapoport (Microsoft)" A vmalloc allocation is preserved using binary structure similar to global KHO memory tracker. It's a linked list of pages where each page is an array of physical address of pages in vmalloc area. kho_preserve_vmalloc() hands out the physical address of the head

[PATCH v3 0/2] kho: add support for preserving vmalloc allocations

From: "Mike Rapoport (Microsoft)" Hi, Following the discussion about preservation of memfd with LUO [1] these patches add support for preserving vmalloc allocations. Any KHO uses case presumes that there's a data structure that lists physical addresses of preserved folios (and potentially some

Re: [PATCH v2 0/2] kho: add support for preserving vmalloc allocations

Argh, I've messed up the posting :( Sorry for the noise. On Sun, Sep 07, 2025 at 10:00:17AM +0300, Mike Rapoport wrote: > From: "Mike Rapoport (Microsoft)" > > Hi, > > Following the discussion about preservation of memfd with LUO [1] these > patches add support for preserving vmalloc allocation