0659df6fad
This prevents a situation where other thread modifies map entries permissions between setting max_prot, then relocking, then setting prot, confusing the operation outcome. E.g. you can get an error that is not possible if operation is performed atomic. Also enable setting rwx for max_prot even if map does not allow to set effective rwx protection. Reviewed by: brooks, markj (previous version) Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D28117 |
||
---|---|---|
.. | ||
imgact_linux.c | ||
linux_copyout.c | ||
linux_dummy_machdep.c | ||
linux_genassym.c | ||
linux_locore.asm | ||
linux_machdep.c | ||
linux_proto.h | ||
linux_ptrace.c | ||
linux_syscall.h | ||
linux_syscalls.c | ||
linux_sysent.c | ||
linux_systrace_args.c | ||
linux_sysvec.c | ||
linux_vdso.lds.s | ||
linux.h | ||
Makefile | ||
syscalls.conf | ||
syscalls.master |