04e4f2b18c
The current code will load the stack size and protection markings, but then only use the markings in the MMU code path. The NOMMU code path always passes PROT_EXEC to the mmap() call. While this doesn't matter to most people whilst the code is running, it will cause a pointless icache flush when starting every FDPIC application. Typically this icache flush will be of a region on the order of 128KB in size, or may be the entire icache, depending on the facilities available on the CPU. In the case where the arch default behaviour seems to be desired (EXSTACK_DEFAULT), we probe VM_STACK_FLAGS for VM_EXEC to determine whether we should be setting PROT_EXEC or not. For arches that support an MPU (Memory Protection Unit - an MMU without the virtual mapping capability), setting PROT_EXEC or not will make an important difference. It should be noted that this change also affects the executability of the brk region, since ELF-FDPIC has that share with the stack. However, this is probably irrelevant as NOMMU programs aren't likely to use the brk region, preferring instead allocation via mmap(). Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: David Howells <dhowells@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
19 lines
423 B
C
19 lines
423 B
C
/*
|
||
* Copyright 2004-2009 Analog Devices Inc.
|
||
*
|
||
* Licensed under the GPL-2 or later.
|
||
*/
|
||
|
||
#ifndef _BLACKFIN_PAGE_H
|
||
#define _BLACKFIN_PAGE_H
|
||
|
||
#include <asm-generic/page.h>
|
||
#define MAP_NR(addr) (((unsigned long)(addr)-PAGE_OFFSET) >> PAGE_SHIFT)
|
||
|
||
#define VM_DATA_DEFAULT_FLAGS \
|
||
(VM_READ | VM_WRITE | \
|
||
((current->personality & READ_IMPLIES_EXEC) ? VM_EXEC : 0 ) | \
|
||
VM_MAYREAD | VM_MAYWRITE | VM_MAYEXEC)
|
||
|
||
#endif
|