]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ARM: 7931/1: Correct virt_addr_valid
authorLaura Abbott <lauraa@codeaurora.org>
Sat, 21 Dec 2013 00:03:06 +0000 (01:03 +0100)
committerJiri Slaby <jslaby@suse.cz>
Thu, 9 Apr 2015 12:13:41 +0000 (14:13 +0200)
commiteec585a2565ee1d56e92e1e80d612cd00ba05887
treee2fc2a3de6694785d78b808e5c516ec8a571b8b0
parent69f8bfe920fe43ea08fbd41dfdb5c0dad337ac46
ARM: 7931/1: Correct virt_addr_valid

commit efea3403d4b7c6d1dd5d5ac3234c161e8b314d66 upstream.

The definition of virt_addr_valid is that virt_addr_valid should
return true if and only if virt_to_page returns a valid pointer.
The current definition of virt_addr_valid only checks against the
virtual address range. There's no guarantee that just because a
virtual address falls bewteen PAGE_OFFSET and high_memory the
associated physical memory has a valid backing struct page. Follow
the example of other architectures and convert to pfn_valid to
verify that the virtual address is actually valid. The check for
an address between PAGE_OFFSET and high_memory is still necessary
as vmalloc/highmem addresses are not valid with virt_to_page.

Cc: Will Deacon <will.deacon@arm.com>
Cc: Nicolas Pitre <nico@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
arch/arm/include/asm/memory.h