diff options
author | 2014-02-24 17:30:55 +0100 | |
---|---|---|
committer | 2014-02-28 18:06:25 +1100 | |
commit | f5295bd8ea8a65dc5eac608b151386314cb978f1 (patch) | |
tree | 826f84e36044824ce00d8af118afc720078e37e8 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | powerpc/le: Ensure that the 'stop-self' RTAS token is handled correctly (diff) | |
download | linux-dev-f5295bd8ea8a65dc5eac608b151386314cb978f1.tar.xz linux-dev-f5295bd8ea8a65dc5eac608b151386314cb978f1.zip |
powerpc/crashdump : Fix page frame number check in copy_oldmem_page
In copy_oldmem_page, the current check using max_pfn and min_low_pfn to
decide if the page is backed or not, is not valid when the memory layout is
not continuous.
This happens when running as a QEMU/KVM guest, where RTAS is mapped higher
in the memory. In that case max_pfn points to the end of RTAS, and a hole
between the end of the kdump kernel and RTAS is not backed by PTEs. As a
consequence, the kdump kernel is crashing in copy_oldmem_page when accessing
in a direct way the pages in that hole.
This fix relies on the memblock's service memblock_is_region_memory to
check if the read page is part or not of the directly accessible memory.
Signed-off-by: Laurent Dufour <ldufour@linux.vnet.ibm.com>
Tested-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
CC: <stable@vger.kernel.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions