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 0/6] Fix --mem-usage /proc/kcore
Date: Mon, 6 Feb 2017 17:31:45 +0530 [thread overview]
Message-ID: <cover.1486381805.git.panand@redhat.com> (raw)
`makedumpfile --mem-usage /proc/kcore` has been broken after kaslr specific
modifications. I have proposed a kernel patch [0] which has been ACKed by
Andrew Morton and is available in next-2017020 now. Hopefully, it should be
part of upstream in v4.10 release. This kernel patch helps to fix this
issue for both the case of kaslr enabled and disabled.
To seek other's feedback, I am sending makedumpfile patches before kernel
patch hits upstream.
[0] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?h=next-20170206&id=c9d4e5d7b7fd6c74e134ca44df8a5386efbc561c
Baoquan He (2):
makedumpfile: Correct the calculation of kvaddr in
set_kcore_vmcoreinfo
makedumpfile: Discard process_dump_load
Pratyush Anand (4):
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
arch/x86_64.c | 6 ++++--
elf_info.c | 25 +++++--------------------
makedumpfile.c | 12 ++++++------
3 files changed, 15 insertions(+), 28 deletions(-)
--
2.9.3
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2017-02-06 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 12:01 Pratyush Anand [this message]
2017-02-06 12:01 ` [Makedumpfile Patch 1/6] show_mem_usage(): calculate page offset after elf load Pratyush Anand
2017-02-06 12:01 ` [Makedumpfile Patch 2/6] initial(): call cach_init() a bit early Pratyush Anand
2017-02-06 12:01 ` [Makedumpfile Patch 3/6] x86_64: check physical address in PT_LOAD for none direct mapped regions Pratyush Anand
2017-02-06 12:01 ` [Makedumpfile Patch 4/6] elf_info: kcore: check for invalid physical address Pratyush Anand
2017-02-06 12:01 ` [Makedumpfile Patch 5/6] makedumpfile: Correct the calculation of kvaddr in set_kcore_vmcoreinfo Pratyush Anand
2017-02-06 12:01 ` [Makedumpfile Patch 6/6] makedumpfile: Discard process_dump_load Pratyush Anand
2017-02-13 6:26 ` [Makedumpfile Patch 0/6] Fix --mem-usage /proc/kcore Atsushi Kumagai
2017-02-13 7:34 ` Pratyush Anand
2017-02-13 8:28 ` Atsushi Kumagai
2017-02-14 4:43 ` 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.1486381805.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox