diff options
| author | Homu <homu@barosl.com> | 2017-03-20 08:54:59 +0900 |
|---|---|---|
| committer | Homu <homu@barosl.com> | 2017-03-20 08:54:59 +0900 |
| commit | 0eef6515f265428e522eea3e2aa3dd936398c4e0 (patch) | |
| tree | ff30e1b77a15c42441c15dd094ca54e886f759ba /src/sys/syscall.rs | |
| parent | 5c9028941285c5f678f16591bb7dba5fc88efe6b (diff) | |
| parent | 902f281981c6495ce4f7d46cec937e00b170a6bf (diff) | |
| download | nix-0eef6515f265428e522eea3e2aa3dd936398c4e0.zip | |
Auto merge of #559 - kevinmehall:mmap, r=kamalmarhubi
Actually mark mmap and related functions as `unsafe`
The nix::sys::mman::mmap documentation says
> Calls to mmap are inherently unsafe, so they must be made in an unsafe
block.
however, the function was not actually marked unsafe.
* `munmap` should also be `unsafe` for obvious reasons.
* `madvise` should be `unsafe` because of the `MADV_DONTNEED` flag.
* `mlock` was already marked `unsafe`
* `munlock` and `msync` don't strictly need to be `unsafe` despite
taking pointers AFAICT, but are marked `unsafe` for consistency and in
case they add additional flags in the future.
[breaking-change]
Diffstat (limited to 'src/sys/syscall.rs')
0 files changed, 0 insertions, 0 deletions