| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
568: Add process_vm_readv and process_vm_writev r=asomers a=geofft
|
|
787: Omit invalid waitpid flags on OpenBSD r=Susurrus a=worr
OpenBSD doesn't have `WEXITED`, `WSTOPPED`, or `WNOWAIT`, so omit those
from that platform.
|
|
|
|
OpenBSD doesn't have `WEXITED`, `WSTOPPED`, or `WNOWAIT`, so omit those
from that platform.
|
|
792: Use libc_enum! where possible r=Susurrus a=wginolas
Some enums which use different names for values than libc still set the
discriminators manually.
closes #254
|
|
|
|
|
|
771: ptrace: add PTRACE_O_EXITKILL option r=Susurrus a=bpowers
It is a somewhat newer option -- it requires Linux 3.8. Is there a
more precise way to specify that?
|
|
794: Migrate memfd constants to libc r=Susurrus a=Susurrus
This will fail because rust-lang/libc#836 is not merged yet, but just getting it staged for when it is.
|
|
|
|
Some enums which use different names for values than libc still set the
discriminators manually.
closes #254
|
|
790: Fix netbsd kevent for breakage introduced by libc r=asomers a=Susurrus
|
|
The datatype for kevent.filter is u32 on NetBSD and
i16 on all other supported platforms. This was recently
fixed in upstream libc, breaking this API, so this
fixes it.
This change also modernizes the code a bit to unify the
EventFilter datatype across platforms and switch to the
libc_enum! macro.
|
|
|
|
|
|
It is a somewhat newer option -- it requires Linux 3.8.
|
|
780: Add a test for ppoll r=Susurrus a=asomers
|
|
782: Fix formatting in CHANGELOG.md r=posborne a=asomers
|
|
783: Promote i686-unknown-freebsd to Tier1 in the README r=Susurrus a=asomers
We effectively made it Tier1 back in
ec6fe0629df87d8355cbdba8b7a0855934a5ac9e, but never updated the README.
|
|
We effectively made it Tier1 back in
ec6fe0629df87d8355cbdba8b7a0855934a5ac9e, but never updated the README.
|
|
|
|
|
|
774: #602 added unistd::mkfifo r=asomers a=jpastuszek
Since libc has mkfifo already I have just copied mkdir and adapted to mkfifo. I have tested that on MacOS only.
|
|
|
|
778: Replace most Linux man page links with Open Group man page links r=posborne a=asomers
But leave in place Linux links for non-standard functions. Also, add
brief docs for some functions that were lacking them.
|
|
768: Add support for 'fallocate' r=asomers a=SanchayanMaity
For #596
|
|
But leave in place Linux links for non-standard functions. Also, add
brief docs for some functions that were lacking them.
|
|
|
|
|
|
773: Add more accessors for AioCb r=asomers a=asomers
|
|
775: Fix test warnings r=asomers a=SanchayanMaity
|
|
This fixes the following warning during run of cargo test
warning: variable does not need to be mutable
--> test/sys/test_aio.rs:16:13
|
16 | fn poll_aio(mut aiocb: &mut AioCb) -> Result<()> {
| ^^^^^^^^^
|
= note: #[warn(unused_mut)] on by default
|
|
gcc::Config has been renamed to gcc::Build
This fixes the following warning during run of cargo test
warning: use of deprecated item: gcc::Config has been renamed to gcc::Build
--> nix-test/build.rs:16:5
|
16 | gcc::Config::new()
| ^^^^^^^^^^^^^^^^
|
= note: #[warn(deprecated)] on by default
|
|
|
|
663: Add support for SO_TIMESTAMP r=asomers a=Wolvereness
This was implemented as part of my employment, and I have received permission to submit it upstream under my own name.
I implemented this with a bit of copy+pasting from the SCM_RIGHTS implementation, and it appeared to be functional when originally implemented on top of 13deb619c3e0bdf490511cedd848e60633ca3b2d (tagged v0.8.0).
|
|
test/test_stat.rs: test correct stat function
|
|
use better merge algorithm for CHANGELOG.md
|
|
|
|
see also: https://about.gitlab.com/2015/02/10/gitlab-reduced-merge-conflicts-by-90-percent-with-changelog-placeholders/
|
|
|
|
|
|
715: Fix multiple issues with POSIX AIO r=asomers a=asomers
Fixed error handling in `AioCb::fsync`, `AioCb::read`, and `AioCb::write`
Previously, the `AioCb`'s `in_progress` field would erroneously be set
to `true`, even if the syscall had an error
Fixes #714
AioCb::Drop will now panic for in-progress AioCb
Printing a warning message to stderr isn't really appropriate, because
there's no way to guarantee that stderr is even valid. Nor is
aio_suspend necessarily an appropriate action to take.
|
|
Previously, the `AioCb`'s `in_progress` field would erroneously be set
to `true`, even if the syscall had an error
Fixes #714
|
