From: Takao Indoh <indou.takao@jp.fujitsu.com>
To: ats-kumagai@wm.jp.nec.com, d.hatayama@jp.fujitsu.com
Cc: kexec@lists.infradead.org
Subject: Re: [makedumpfile PATCH v2 0/3] Fix KASLR problem on sadump
Date: Tue, 24 Oct 2017 19:00:47 +0900 [thread overview]
Message-ID: <20171024100046.GF19620@tindoh2.g01.fujitsu.local> (raw)
In-Reply-To: <20171016094217.1020-1-indou.takao@jp.fujitsu.com>
Hi Kumagai-san, Hatayama-san,
Any comments?
Thanks,
Takao Indoh
On Mon, Oct 16, 2017 at 06:42:14PM +0900, Takao Indoh wrote:
> Hi Kumagai-san, Hatayama-san,
>
> Hatayama-san, thanks for your review, I updated may patch.
>
> These patch series fix a problem that makedumpfile cannot handle a dumpfile
> which is captured by sadump on KASLR enabled kernel.
>
> When KASLR feature is enabled, a kernel is placed on the memory randomly and
> therefore makedumpfile cannot handle a dumpfile because addresses of kernel
> symbols in vmlinux are different from actual addresses. In the case of kdump,
> information to get actual address is included in the vmcoreinfo, but dumpfile of
> sadump does not have such a information.
>
> These patches calculate kaslr offset and phys_base to solve this problem. The
> basic idea is getting register (IDTR and CR3) from dump header, and calculate
> kaslr_offset/phys_base using them.
>
> changelog:
> v2:
> - Change get_vec0_addr style
> - Some tiny fixes
>
> v1:
> http://lists.infradead.org/pipermail/kexec/2017-October/019530.html
>
> Takao Indoh (3):
> Support symbol __cpu_online_mask
> Introduce vtop4_x86_64_pagetable
> sadump: Fix a KASLR problem of sadump
>
> arch/x86_64.c | 30 ++++-
> makedumpfile.c | 20 ++-
> makedumpfile.h | 8 +-
> sadump_info.c | 418 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 4 files changed, 463 insertions(+), 13 deletions(-)
>
> --
> 2.9.5
>
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-10-24 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 9:42 [makedumpfile PATCH v2 0/3] Fix KASLR problem on sadump Takao Indoh
2017-10-16 9:42 ` [makedumpfile PATCH v2 1/3] Support symbol __cpu_online_mask Takao Indoh
2017-10-16 9:42 ` [makedumpfile PATCH v2 2/3] Introduce vtop4_x86_64_pagetable Takao Indoh
2017-10-16 9:42 ` [makedumpfile PATCH v2 3/3] sadump: Fix a KASLR problem of sadump Takao Indoh
2017-10-26 0:16 ` Atsushi Kumagai
2017-10-26 1:19 ` Takao Indoh
2017-10-24 10:00 ` Takao Indoh [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=20171024100046.GF19620@tindoh2.g01.fujitsu.local \
--to=indou.takao@jp.fujitsu.com \
--cc=ats-kumagai@wm.jp.nec.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
/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