From: Pratyush Anand <panand@redhat.com>
To: ats-kumagai@wm.jp.nec.com
Cc: dyoung@redhat.com, kexec@lists.infradead.org, bhe@redhat.com
Subject: Re: [Makedumpfile Patch v2 0/7] Fix --mem-usage /proc/kcore
Date: Tue, 28 Feb 2017 20:35:32 +0530 [thread overview]
Message-ID: <83f4e5aa-1376-e387-a986-98c4306ff0a7@redhat.com> (raw)
In-Reply-To: <cover.1488260510.git.panand@redhat.com>
On Tuesday 28 February 2017 11:22 AM, Pratyush Anand wrote:
> `makedumpfile --mem-usage /proc/kcore` has been broken after kaslr specific
> modifications. A kernel patch has been ACKed by Andrew Morton and has been
> sent to Linus now [0]. This kernel patch helps to fix the issue for both
> the case of kaslr enabled and disabled.
>
> [0] http://marc.info/?l=linux-mm-commits&m=148823497215968&w=2
Just FYI,patch is in upstream now.
commit 464920104bf7adac12722035bfefb3d772eb04d8
Author: Pratyush Anand <panand@redhat.com>
Date: Mon Feb 27 14:27:31 2017 -0800
/proc/kcore: update physical address for kcore ram and text
>
> 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.c | 18 ++++++++++++------
> 3 files changed, 21 insertions(+), 28 deletions(-)
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-02-28 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 5:52 [Makedumpfile Patch v2 0/7] Fix --mem-usage /proc/kcore Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 1/7] show_mem_usage(): calculate page offset after elf load Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 2/7] initial(): call cach_init() a bit early Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 3/7] x86_64: check physical address in PT_LOAD for none direct mapped regions Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 4/7] elf_info: kcore: check for invalid physical address Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 5/7] makedumpfile: Correct the calculation of kvaddr in set_kcore_vmcoreinfo Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 6/7] makedumpfile: Discard process_dump_load Pratyush Anand
2017-02-28 5:52 ` [Makedumpfile Patch v2 7/7] mem-usage: allow to work only with -f for kernel version < 4.11 Pratyush Anand
2017-03-02 4:49 ` Atsushi Kumagai
2017-03-02 5:47 ` Pratyush Anand
2017-03-02 5:48 ` Pratyush Anand
2017-03-02 7:29 ` Atsushi Kumagai
2017-02-28 15:05 ` Pratyush Anand [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=83f4e5aa-1376-e387-a986-98c4306ff0a7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox