Age | Commit message (Collapse) | Author |
|
* enabled as much functionality and defines that match
updated libc definitions for haiku
|
|
No documentation provided for MADV_CAN_REUSE, as Darwin doesn't actually
document its functionality.
|
|
|
|
The previous documentation described the default behavior, rather than
the behavior when the flag was set.
Also fix a test which is failing due to passing this flag erroneously.
|
|
Using features reduces build time and size for consumer crates. By
default all features are enabled.
|
|
1601: Update `mman` related docs r=rtzoeller a=schctl
Added docs for `memfd_create`, `shm_open`, and `shm_unlink`, and some man-page and intra doc links.
Co-authored-by: Sachin Cherian <sachinctl@protonmail.com>
|
|
- Add docs for `memfd_create`, `shm_open`, and `shm_unlink`
- Add man-page links
- Remove` #[allow(missing_docs)]`on the `memfd` module
|
|
|
|
Rust has no "ppc" target_arch. It should be "powerpc" or "powerpc64".
|
|
This was an oversight from #1306.
Reported-by: @ocadaruma
|
|
1531: mman add MAP_CONCEAL mmap flag for openbsd r=asomers a=devnexen
Co-authored-by: David Carlier <devnexen@gmail.com>
|
|
|
|
1532: mman MAP_JIT flag documentation. r=asomers a=devnexen
Co-authored-by: David Carlier <devnexen@gmail.com>
|
|
1522: mman mod adding MAP_ALIGNED_SUPER flag for freebsd. r=asomers a=devnexen
Co-authored-by: David Carlier <devnexen@gmail.com>
|
|
And this time, start running Clippy in CI
|
|
|
|
|
|
|
|
1520: mman module netbsd additions. r=asomers a=devnexen
1523: mman: add MAP_STACK to openbsd which is needed … r=asomers a=devnexen
…to created stack mappings
Co-authored-by: David Carlier <devnexen@gmail.com>
|
|
|
|
|
|
|
|
Since libc may add new variants at any time, Nix's consumers should not
use exhaustive match patterns.
Fixes #1182
|
|
For many of Nix's consumers it be convenient to easily convert a Nix
error into a std::io::Error. That's currently not possible because of
the InvalidPath, InvalidUtf8, and UnsupportedOperation types that have
no equivalent in std::io::Error.
However, very few of Nix's public APIs actually return those unusual
errors. So a more useful API would be for Nix's standard error type to
implement Into<std::io::Error>.
This commit makes Error a simple NewType around Errno. For most
functions it's a drop-in replacement. There are only three exceptions:
* clearenv now returns a bespoke error type. It was the only Nix
function whose error couldn't be cleanly mapped onto an Errno.
* sys::signal::signal now returns Error(Errno::ENOTSUP) instead of
Error::UnsupportedOperation when the user passes an incompatible
argument to `handler`.
* When a NixPath exceeds PATH_MAX, it will now return
Error(Errno::ENAMETOOLONG) instead of Error::InvalidPath.
In the latter two cases there is now some abiguity about whether the
error code was generated by Nix or by the OS. But I think the ambiguity
is worth it for the sake of being able to implement Into<io::Error>.
This commit also introduces Error::Sys() as a migration aid. Previously
that as an enum variant. Now it's a function, but it will work in many
of the same contexts as the original.
Fixes #1155
|
|
|
|
|
|
|
|
|
|
Closes #1194
Use git libc for development
(Remember to reset this to released version for the next nix release, once libc has released >=0.2.69)
|
|
libc just undefined MADV_SOFT_OFFLINE on mips.
https://github.com/rust-lang/libc/pull/1365
Fixes #1074
|
|
|
|
try! is not available in Rust 2018
|
|
|
|
|
|
|
|
|
|
|
|
806: Cleanup all doc warnings r=asomers a=Susurrus
With the impending switch to Pulldown as the default doc generator, warnings
have been enabled for incompatible syntax. This fixes all of said warnings.
|
|
With the impending switch to Pulldown as the default doc generator, warnings
have been enabled for incompatible syntax. This fixes all of said warnings.
|
|
cc #664 (unsure if this is everything needed)
|
|
|
|
|
|
|
|
|
|
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.
|
|
Prefer libc_bitflags! over bitflags!. Prefer libc::CONSTANTS over
writing the constant manually.
|
|
|
|
|
|
This serves as an example use of the libc_bitflags macro.
|
|
|