summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2016-03-10 01:08:32 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2016-03-10 02:43:42 +0300
commitac343e882a8377caef5fa75d9093cb77e9d4bf6d (patch)
treedbed5dafd7715f1fac5e83670eddc8f9a57548d8 /mm
parent0a2e280b6d8ea4afef07c749070705d6af403b7f (diff)
downloadlinux-ac343e882a8377caef5fa75d9093cb77e9d4bf6d.tar.xz
memremap: check pfn validity before passing to pfn_to_page()
In memremap's helper function try_ram_remap(), we dereference a struct page pointer that was derived from a PFN that is known to be covered by a 'System RAM' iomem region, and is thus assumed to be a 'valid' PFN, i.e., a PFN that has a struct page associated with it and is covered by the kernel direct mapping. However, the assumption that there is a 1:1 relation between the System RAM iomem region and the kernel direct mapping is not universally valid on all architectures, and on ARM and arm64, 'System RAM' may include regions for which pfn_valid() returns false. Generally speaking, both __va() and pfn_to_page() should only ever be called on PFNs/physical addresses for which pfn_valid() returns true, so add that check to try_ram_remap(). Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions