From: Aneesh Kumar K V <aneesh.kumar@kernel.org>
To: Sourabh Jain <sourabhjain@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>,
linuxppc-dev@ozlabs.org
Cc: Aditya Gupta <adityag@linux.ibm.com>,
Mahesh Salgaonkar <mahesh@linux.ibm.com>,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [PATCH v5 1/3] powerpc: make fadump resilient with memory add/remove events
Date: Wed, 22 Nov 2023 17:50:30 +0530 [thread overview]
Message-ID: <47a119c1-05e9-47fb-9cc7-85aa7e1e4ae7@kernel.org> (raw)
In-Reply-To: <e65c4dd0-df97-481d-b3e9-0088f2c9b2ea@linux.ibm.com>
On 11/22/23 4:05 PM, Sourabh Jain wrote:
> Hello Michael,
>
>
> On 22/11/23 10:47, Michael Ellerman wrote:
>> Aneesh Kumar K V <aneesh.kumar@linux.ibm.com> writes:
>> ...
>>> I am not sure whether we need to add all the complexity to enable supporting different fadump kernel
>>> version. Is that even a possible use case with fadump? Can't we always assume that with fadump the
>>> crash kernel and fadump kernel will be same version?
>> How sure are we of that?
>>
>> Don't we go through grub when we boot into the 2nd kernel. And so
>> couldn't it choose to boot a different kernel, for whatever reason.
>>
>> I don't think we need to support different pt_reg / cpumask sizes, but
>> requiring the exact same kernel version is too strict I think.
> Agree.
>>
>> But maybe I'm wrong. Would be good to hear what distro folks think.
>
> How about checking fadump crash info header compatibility in the following way?
>
> static bool is_fadump_header_compatible(struct fadump_crash_info_header *fdh)
> {
> if (fdh->magic_number == FADUMP_CRASH_INFO_MAGIC_OLD) {
> pr_err("Old magic number, can't process the dump.");
> return false;
> }
>
> if (fdh->magic_number != FADUMP_CRASH_INFO_MAGIC) {
> pr_err("Fadump header is corrupted.");
> return false;
> }
>
> /*
> * If the kernel version of the first/crashed kernel and the second/fadump
> * kernel is not same, then only collect the dump if the size of all
> * non-primitive type members of the fadump header is the same across kernels.
> */
> if (strcmp(fdh->kernel_version, init_uts_ns.name.release)) {
> if (fdh->pt_regs_sz != sizeof(struct pt_regs) || fdh->cpu_mask_sz != sizeof(struct cpumask)) {
> pr_err("Fadump header size mismatch.\n")
> return false;
> } else
> pr_warn("Kernel version mismatch; dump data is unreliable.\n");
> }
>
You also want a fdh->version check? I am still not sure you need the kernel_version check. IMHO that is too strict
and can hit that check where you have kexec kernel which is not installed in /boot crashing?
> return true;
> }
>
> And the new fadump crash info header will be: As suggested by Hari.
>
> /* fadump crash info structure */
> struct fadump_crash_info_header {
> u64 magic_number;
> + u32 version;
> u32 crashing_cpu;
> u64 elfcorehdr_addr;
> + u64 elfcorehdr_size;
> + u64 vmcoreinfo_raddr;
> + u64 vmcoreinfo_size;
> + u8 kernel_version[__NEW_UTS_LEN + 1];
> + u32 pt_regs_sz;
> struct pt_regs regs;
> + u32 cpu_mask_sz;
> struct cpumask cpu_mask;
> };
>
> Thanks,
> Sourabh Jain
next prev parent reply other threads:[~2023-11-22 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 12:45 [PATCH v5 0/3] powerpc: make fadump resilient with memory add/remove events Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 1/3] " Sourabh Jain
2023-11-09 12:14 ` Michael Ellerman
2023-11-13 6:42 ` Sourabh Jain
2023-11-15 4:44 ` Aneesh Kumar K.V
2023-11-17 4:33 ` Sourabh Jain
2023-11-17 5:31 ` Aneesh Kumar K V
2023-11-17 6:14 ` Hari Bathini
2023-11-22 5:17 ` Michael Ellerman
2023-11-22 10:35 ` Sourabh Jain
2023-11-22 12:20 ` Aneesh Kumar K V [this message]
2023-11-24 5:20 ` Sourabh Jain
2023-11-22 12:52 ` Michael Ellerman
2023-11-24 7:21 ` Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 2/3] powerpc/fadump: add hotplug_ready sysfs interface Sourabh Jain
2023-10-29 12:45 ` [PATCH v5 3/3] Documentation/powerpc: update fadump implementation details Sourabh Jain
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=47a119c1-05e9-47fb-9cc7-85aa7e1e4ae7@kernel.org \
--to=aneesh.kumar@kernel.org \
--cc=adityag@linux.ibm.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=sourabhjain@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;
as well as URLs for NNTP newsgroup(s).