kexec.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: kumagai-atsushi@mxc.nes.nec.co.jp
Cc: dyoung@redhat.com, kexec@lists.infradead.org,
	thgarnie@google.com, Baoquan He <bhe@redhat.com>,
	tonli@redhat.com
Subject: [PATCH v2 0/3] makedumpfile: Add support of mm randomization
Date: Thu,  6 Oct 2016 17:50:05 +0800	[thread overview]
Message-ID: <1475747408-25666-1-git-send-email-bhe@redhat.com> (raw)

This is v2 post.

Because of Thomas's kernel patchset, direct mapping, vmalloc and vmemmap
could have random starting address. They need be exported to VMCOREINFO
and let makedumpfile know this so that makedumpfile can identify these
memory areas correctly.

Below is the kernel patchset from Thomas:
x86/mm: memory area address KASLR 
https://lwn.net/Articles/692289/

I have posted a new kernel patchset to export the base of direct mapping,
vmalloc and vmemmap. The subject is:
kexec: Export memory sections virtual addresses to vmcoreinfo

v1->v2:
    According to Atsushi's comment, mainly change patch 3/3.
    - Remove VMALLOC_END_ORIG, VMEMMAP_END_ORIG , VMALLOC_END_2_6_31
      and VMEMMAP_END_2_6_31 since they are not needed anymore.
    - Put those number table member value assignment into
      get_versiondep_info_x86_64.

Baoquan He (3):
  makedumpfile: Get info->kernel_version from SYMBOL(init_uts_ns)
    earlier
  makedumpfile: Move get_versiondep_info calling earlier
  makedumpfile: Add support for MM randomization

 arch/x86_64.c  | 51 ++++++++++++++++++++++++++++++++++-----------------
 makedumpfile.c | 33 ++++++++++++++++-----------------
 makedumpfile.h |  7 +++----
 3 files changed, 53 insertions(+), 38 deletions(-)

-- 
2.5.5


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

             reply	other threads:[~2016-10-06  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  9:50 Baoquan He [this message]
2016-10-06  9:50 ` [PATCH v2 1/3] makedumpfile: Get info->kernel_version from SYMBOL(init_uts_ns) earlier Baoquan He
2016-10-06  9:50 ` [PATCH v2 2/3] makedumpfile: Move get_versiondep_info calling earlier Baoquan He
2016-10-06  9:50 ` [PATCH v2 3/3] makedumpfile: Add support for MM randomization Baoquan He
2016-10-06 10:23 ` [PATCH v2 0/3] makedumpfile: Add support of mm randomization Baoquan He

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=1475747408-25666-1-git-send-email-bhe@redhat.com \
    --to=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=thgarnie@google.com \
    --cc=tonli@redhat.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).