All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: ats-kumagai@wm.jp.nec.com
Cc: Pratyush Anand <panand@redhat.com>,
	dyoung@redhat.com, kexec@lists.infradead.org, bhe@redhat.com
Subject: [Makedumpfile Patch v3 0/7] Fix --mem-usage /proc/kcore
Date: Thu,  2 Mar 2017 14:06:45 +0530	[thread overview]
Message-ID: <cover.1488443170.git.panand@redhat.com> (raw)


`makedumpfile --mem-usage /proc/kcore` has been broken after kaslr specific
modifications. Kernel commit commit 464920104bf7 (/proc/kcore: update
physical address for kcore ram and text) provides now valid physical
address for direct mapped regions and invalid (-1) for other areas.  This
helps to fix the issue in makedumpfile for both the case of kaslr enabled
and disabled.

Changes since v2:
 - Fixed a memory leak issue and updated man page and usage info
Changes since v1:
 - One more patch..Now mem-usage with older kernel (< 4.11) will only work
   when that has been rightly patched and -f has been used in makedumpfile
   command line.


Baoquan He (2):
  makedumpfile: Correct the calculation of kvaddr in
    set_kcore_vmcoreinfo
  makedumpfile: Discard process_dump_load

Pratyush Anand (5):
  show_mem_usage(): calculate page offset after elf load
  initial(): call cach_init() a bit early
  x86_64: check physical address in PT_LOAD for none direct mapped
    regions
  elf_info: kcore: check for invalid physical address
  mem-usage: allow to work only with -f for kernel version < 4.11

 arch/x86_64.c  |  6 ++++--
 elf_info.c     | 25 +++++--------------------
 makedumpfile.8 |  9 ++++++++-
 makedumpfile.c | 18 ++++++++++++------
 print_info.c   |  3 ++-
 5 files changed, 31 insertions(+), 30 deletions(-)

-- 
2.9.3


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

             reply	other threads:[~2017-03-02  8:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02  8:36 Pratyush Anand [this message]
2017-03-02  8:36 ` [Makedumpfile Patch v3 1/7] show_mem_usage(): calculate page offset after elf load Pratyush Anand
2017-03-02  8:36 ` [Makedumpfile Patch v3 2/7] initial(): call cach_init() a bit early Pratyush Anand
2017-07-19  7:46   ` Atsushi Kumagai
2017-07-19 11:20     ` Pratyush Anand
2017-07-20  6:54       ` Atsushi Kumagai
2017-07-20  8:01         ` Hatayama, Daisuke
2017-03-02  8:36 ` [Makedumpfile Patch v3 3/7] x86_64: check physical address in PT_LOAD for none direct mapped regions Pratyush Anand
2017-03-02  8:36 ` [Makedumpfile Patch v3 4/7] elf_info: kcore: check for invalid physical address Pratyush Anand
2017-03-02  8:36 ` [Makedumpfile Patch v3 5/7] makedumpfile: Correct the calculation of kvaddr in set_kcore_vmcoreinfo Pratyush Anand
2017-03-02  8:36 ` [Makedumpfile Patch v3 6/7] makedumpfile: Discard process_dump_load Pratyush Anand
2017-03-02  8:36 ` [Makedumpfile Patch v3 7/7] mem-usage: allow to work only with -f for kernel version < 4.11 Pratyush Anand
2017-03-03  2:10   ` Atsushi Kumagai
2017-03-03  2:48     ` Pratyush Anand
2017-03-03  3:07       ` bhe
2017-03-03  4:35         ` Atsushi Kumagai
2017-03-03  4:56           ` Pratyush Anand

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=cover.1488443170.git.panand@redhat.com \
    --to=panand@redhat.com \
    --cc=ats-kumagai@wm.jp.nec.com \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.