diff options
author | Catalin Marinas <catalin.marinas@arm.com> | 2020-02-19 12:31:56 +0000 |
---|---|---|
committer | Will Deacon <will@kernel.org> | 2020-02-20 10:03:14 +0000 |
commit | dcde237319e626d1ec3c9d8b7613032f0fd4663a (patch) | |
tree | fba292b1a70328443aa982471c65a28c2ea28572 /include/media/i2c/mt9v022.h | |
parent | ce4a64e1f656138e2a1481049ea554720f86b43a (diff) | |
download | linux-dcde237319e626d1ec3c9d8b7613032f0fd4663a.tar.bz2 |
mm: Avoid creating virtual address aliases in brk()/mmap()/mremap()
Currently the arm64 kernel ignores the top address byte passed to brk(),
mmap() and mremap(). When the user is not aware of the 56-bit address
limit or relies on the kernel to return an error, untagging such
pointers has the potential to create address aliases in user-space.
Passing a tagged address to munmap(), madvise() is permitted since the
tagged pointer is expected to be inside an existing mapping.
The current behaviour breaks the existing glibc malloc() implementation
which relies on brk() with an address beyond 56-bit to be rejected by
the kernel.
Remove untagging in the above functions by partially reverting commit
ce18d171cb73 ("mm: untag user pointers in mmap/munmap/mremap/brk"). In
addition, update the arm64 tagged-address-abi.rst document accordingly.
Link: https://bugzilla.redhat.com/1797052
Fixes: ce18d171cb73 ("mm: untag user pointers in mmap/munmap/mremap/brk")
Cc: <stable@vger.kernel.org> # 5.4.x-
Cc: Florian Weimer <fweimer@redhat.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Reported-by: Victor Stinner <vstinner@redhat.com>
Acked-by: Will Deacon <will@kernel.org>
Acked-by: Andrey Konovalov <andreyknvl@google.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Will Deacon <will@kernel.org>
Diffstat (limited to 'include/media/i2c/mt9v022.h')
0 files changed, 0 insertions, 0 deletions