summaryrefslogtreecommitdiffstats
path: root/mm/madvise.c
diff options
context:
space:
mode:
authorMike Frysinger <vapier.adi@gmail.com>2010-01-06 17:23:23 +0000
committerLinus Torvalds <torvalds@linux-foundation.org>2010-01-06 18:16:02 -0800
commitcfe79c00a2f4f687eed8b7534d1d3d3d35540c29 (patch)
tree62c603938e7b740ca16ce1012a6ee7ab08b3f727 /mm/madvise.c
parent04e4f2b18c8de1389d1e00fef0f42a8099910daf (diff)
downloadlinux-cfe79c00a2f4f687eed8b7534d1d3d3d35540c29.tar.bz2
NOMMU: Avoiding duplicate icache flushes of shared maps
When working with FDPIC, there are many shared mappings of read-only code regions between applications (the C library, applet packages like busybox, etc.), but the current do_mmap_pgoff() function will issue an icache flush whenever a VMA is added to an MM instead of only doing it when the map is initially created. The flush can instead be done when a region is first mmapped PROT_EXEC. Note that we may not rely on the first mapping of a region being executable - it's possible for it to be PROT_READ only, so we have to remember whether we've flushed the region or not, and then flush the entire region when a bit of it is made executable. However, this also affects the brk area. That will no longer be executable. We can mprotect() it to PROT_EXEC on MPU-mode kernels, but for NOMMU mode kernels, when it increases the brk allocation, making sys_brk() flush the extra from the icache should suffice. The brk area probably isn't used by NOMMU programs since the brk area can only use up the leavings from the stack allocation, where the stack allocation is larger than requested. Signed-off-by: David Howells <dhowells@redhat.com> Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/madvise.c')
0 files changed, 0 insertions, 0 deletions