public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Hari Bathini <hbathini@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>,
	Mahesh Salgaonkar <mahesh@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	Shivang Upadhyay <shivangu@linux.ibm.com>
Subject: Re: [PATCH] powerpc/crash: adjust the elfcorehdr size
Date: Tue, 24 Feb 2026 09:34:46 +0530	[thread overview]
Message-ID: <7061c762-cb20-4ec0-8c7b-2899ecc47503@linux.ibm.com> (raw)
In-Reply-To: <21a8553a-82c8-46f1-93cb-fbdb6ed32377@linux.ibm.com>



On 20/02/26 15:54, Hari Bathini wrote:
>
>
> On 18/02/26 10:31 am, Sourabh Jain wrote:
>> With crash hotplug support enabled, additional memory is allocated to
>> the elfcorehdr kexec segment to accommodate resources added during
>> memory hotplug events. However, the kdump FDT is not updated with the
>> same size, which can result in elfcorehdr corruption in the kdump
>> kernel.
>>
>> Update elf_headers_sz (the kimage member representing the size of the
>> elfcorehdr kexec segment) to reflect the total memory allocated for the
>> elfcorehdr segment instead of the elfcorehdr buffer size at the time of
>> kdump load. This allows of_kexec_alloc_and_setup_fdt() to reserve the
>> full elfcorehdr memory in the kdump FDT and prevents elfcorehdr
>> corruption.
>>
>> Fixes: 849599b702ef8 ("powerpc/crash: add crash memory hotplug support")
>> Cc: Hari Bathini <hbathini@linux.ibm.com>
>> Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
>> Cc: Mahesh Salgaonkar <mahesh@linux.ibm.com>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Cc: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>> Cc: Shivang Upadhyay <shivangu@linux.ibm.com>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>>   arch/powerpc/kexec/file_load_64.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/kexec/file_load_64.c 
>> b/arch/powerpc/kexec/file_load_64.c
>> index e7ef8b2a2554..ed76326f4b57 100644
>> --- a/arch/powerpc/kexec/file_load_64.c
>> +++ b/arch/powerpc/kexec/file_load_64.c
>> @@ -460,7 +460,7 @@ static int load_elfcorehdr_segment(struct kimage 
>> *image, struct kexec_buf *kbuf)
>>       }
>>         image->elf_load_addr = kbuf->mem;
>
>> -    image->elf_headers_sz = headers_sz;
>> +    image->elf_headers_sz = kbuf->memsz;
>
> A comment here explaining why memsz is used instead of headers_sz and
> also, another comment where memsz is set, as to why extra memory size
> is accounted under it, improves readability...

Sure I will update the commit message in the next version.

>
> Regardless..
>
> Reviewed-by: Hari Bathini <hbathini@linux.ibm.com>
Thanks for the review.

- Sourabh Jain


      reply	other threads:[~2026-02-24  4:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  5:01 [PATCH] powerpc/crash: adjust the elfcorehdr size Sourabh Jain
2026-02-20 10:24 ` Hari Bathini
2026-02-24  4:04   ` Sourabh Jain [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7061c762-cb20-4ec0-8c7b-2899ecc47503@linux.ibm.com \
    --to=sourabhjain@linux.ibm.com \
    --cc=hbathini@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=ritesh.list@gmail.com \
    --cc=shivangu@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox