From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Dave Anderson <anderson@redhat.com>
Cc: V Srivatsa <vsrivatsa@in.ibm.com>,
kexec@lists.infradead.org,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>,
Reinhard <BUENDGEN@de.ibm.com>
Subject: Re: makedumpfile: Add erased information in compressed kdump file and ELF formatted dumpfile
Date: Tue, 13 Sep 2011 16:46:45 +0530 [thread overview]
Message-ID: <4E6F3B9D.7060305@linux.vnet.ibm.com> (raw)
In-Reply-To: <682646784.634954.1315851890438.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
On 09/12/2011 11:54 PM, Dave Anderson wrote:
>
> Hi Mahesh,
>
> Now that this feature is in makedumpfile-1.4.0, I presume that you
> have crash utility "warning" patches underway?
Yup. I am working on it, will post the patches very soon.
>
> Also, can you confirm that compressed or kdumps with (or without)
> eraseinfo data can still be handled with no problem by the current
> version of the crash utility? I'm not talking about the ramifications
> of whatever kernel data may have been erased, but whether the changes to
> the dumpfile headers could cause a problem. I'm presuming that the
> compressed kdump eraseinfo data would be invisible to an older version
> of crash, and that ELF kdump eraseinfo would just show up as an (unused)
> ELF note -- but I just want to make sure.
Yes. The changes to dumpfile header and addition of eraseinfo data/ELF
note will not cause any problems with older crash version. With the
current version of crash the ELF kdump eraseinfo note would show up as
below:
Elf64_Nhdr:
n_namesz: 10 ("ERASEINFO")
n_descsz: 56
n_type: 0 (?)
2065736172650000 72616a5f64657263
697320656d616e2e 650a36353220657a
656e692065736172 736f746f72705f74
303120657a697320
Thanks,
-Mahesh.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-09-13 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 20:06 [PATCH v2 7/8] makedumpfile: Add erased information in compressed kdump file Mahesh J Salgaonkar
2011-08-12 8:10 ` Ken'ichi Ohmichi
2011-08-18 8:14 ` Mahesh Jagannath Salgaonkar
2011-08-19 5:39 ` Ken'ichi Ohmichi
2011-08-16 1:00 ` Ken'ichi Ohmichi
2011-08-16 10:16 ` Mahesh Jagannath Salgaonkar
2011-08-19 6:16 ` Ken'ichi Ohmichi
2011-08-22 11:57 ` Mahesh J Salgaonkar
2011-09-06 15:44 ` Mahesh J Salgaonkar
2011-09-07 6:59 ` Ken'ichi Ohmichi
2011-09-12 18:24 ` makedumpfile: Add erased information in compressed kdump file and ELF formatted dumpfile Dave Anderson
2011-09-13 11:16 ` Mahesh Jagannath Salgaonkar [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=4E6F3B9D.7060305@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=BUENDGEN@de.ibm.com \
--cc=ananth@in.ibm.com \
--cc=anderson@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vsrivatsa@in.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