diff options
| author | Lennert Buytenhek <[email protected]> | 2006-07-10 04:45:27 -0700 |
|---|---|---|
| committer | Linus Torvalds <[email protected]> | 2006-07-10 13:24:25 -0700 |
| commit | 06c67befeeb16f2995c11b0e04a348103ddbfab1 (patch) | |
| tree | aad64fa9d2d03b1479885d1c703ccc5890b12afe /include/linux | |
| parent | 49c0dab7e6000888b616bedcbbc8cd4710331610 (diff) | |
[PATCH] make valid_mmap_phys_addr_range() take a pfn
Newer ARMs have a 40 bit physical address space, but mapping physical
memory above 4G needs a special page table format which we (currently?) do
not use for userspace mappings, so what happens instead is that mapping an
address >= 4G will happily discard the upper bits and wrap.
There is a valid_mmap_phys_addr_range() arch hook where we could check for
>= 4G addresses and deny the mapping, but this hook takes an unsigned long
address:
static inline int valid_mmap_phys_addr_range(unsigned long addr, size_t size);
And drivers/char/mem.c:mmap_mem() calls it like this:
static int mmap_mem(struct file * file, struct vm_area_struct * vma)
{
size_t size = vma->vm_end - vma->vm_start;
if (!valid_mmap_phys_addr_range(vma->vm_pgoff << PAGE_SHIFT, size))
So that's not much help either.
This patch makes the hook take a pfn instead of a phys address.
Signed-off-by: Lennert Buytenhek <[email protected]>
Cc: Bjorn Helgaas <[email protected]>
Cc: "Luck, Tony" <[email protected]>
Cc: Russell King <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions