Rich Felker fda365a530 fix mremap memory synchronization and use of variadic argument ...

since mremap with the MREMAP_FIXED flag is an operation that unmaps
existing mappings, it needs to use the vm lock mechanism to ensure
that any in-progress synchronization operations using vm identities
from before the call have finished.

also, the variadic argument was erroneously being read even if the
MREMAP_FIXED flag was not passed. in practice this didn't break
anything, but it's UB and in theory LTO could turn it into a hard
error.

2015-11-02 16:37:51 -05:00

..

madvise.c

global cleanup to use the new syscall interface

2011-03-20 00:16:43 -04:00

mincore.c

mincore syscall wrapper

2012-09-09 16:37:19 -04:00

mlock.c

global cleanup to use the new syscall interface

2011-03-20 00:16:43 -04:00

mlockall.c

global cleanup to use the new syscall interface

2011-03-20 00:16:43 -04:00

mmap.c

redesign and simplify vmlock system

2015-04-10 02:27:52 -04:00

mprotect.c

use weak symbols for the POSIX functions that will be used by C threads

2014-09-06 18:11:24 -04:00

mremap.c

fix mremap memory synchronization and use of variadic argument

2015-11-02 16:37:51 -05:00

msync.c

make fsync, fdatasync, and msync cancellation points

2015-01-30 22:05:40 -05:00

munlock.c

global cleanup to use the new syscall interface

2011-03-20 00:16:43 -04:00

munlockall.c

global cleanup to use the new syscall interface

2011-03-20 00:16:43 -04:00

munmap.c

redesign and simplify vmlock system

2015-04-10 02:27:52 -04:00

posix_madvise.c

fix missing include in posix_madvise.c (compile error)

2011-04-20 15:36:15 -04:00

shm_open.c

fix shm_open wrongly being cancellable

2013-07-20 13:19:14 -04:00