about summary refs log tree commit diff
path: root/library/std/src/sys
AgeCommit message (Collapse)AuthorLines
2020-09-22Revert "Function to convert OpenOptions to c_int"Joshua Nelson-35/+0
2020-09-22Auto merge of #76110 - FedericoPonzi:convert-openoptions-cint, r=JoshTriplettbors-0/+35
Function to convert OpenOptions to c_int Fixes: #74943 The creation_mode and access_mode function were already available in the OpenOptions struct, but currently private. I've added a new free functions to unix/fs.rs which takes the OpenOptions, and returns the c_int to be used as parameter for the `open` call.
2020-09-22enable unstable open_options_ext_as_flags feature in doc commentsFederico Ponzi-0/+1
2020-09-21Rollup merge of #76521 - tavianator:fix-pthread-getattr-destroy, r=AmanieuRalf Jung-2/+8
Fix segfault if pthread_getattr_np fails glibc [destroys][1] the passed pthread_attr_t if pthread_getattr_np() fails. Destroying it again leads to a segfault. Fix it by only destroying it on success for glibc. [1]: https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/pthread_getattr_np.c;h=ce437205e41dc05653e435f6188768cccdd91c99;hb=HEAD#l205
2020-09-20try again to appease tidyWithout Boats-1/+0
2020-09-20spend another CI build to delete a double newlineWithout Boats-1/+0
2020-09-20fix typosWithout Boats-6/+6
2020-09-20Make RawFd implement the RawFd traitsWithout Boats-0/+59
2020-09-19Add tracking issue for feature(unix_socket_peek)rijenkii-3/+3
2020-09-17Auto merge of #76645 - fusion-engineering-forks:windows-lock, r=kennytmbors-43/+41
Small cleanups in Windows Mutex. - Move `held` into the boxed part, since the SRW lock implementation does not use this. This makes the Mutex 50% smaller. - Use `Cell` instead of `UnsafeCell` for `held`, such that `.replace()` can be used. - Add some comments. - Avoid creating multiple `&mut`s to the critical section object in `ReentrantMutex`.
2020-09-16Rollup merge of #76758 - adamlesinski:clone_clock, r=tmandryTyler Mandry-1/+3
[fuchsia] Propagate the userspace UTC clock On Fuchsia, spawning a subprocess does not automatically clone all of the parent process' capabilities. UTC time on Fuchsia is managed by a top-level userspace clock capability that is cloned and passed to subprocesses. This change ensures that any Rust subprocess gets access to the UTC clock, if the parent had access to it. This is critical for tests, which on Fuchsia, use panic=abort and spawn subprocesses per test.
2020-09-16Avoid creating `&mut`s in Windows ReentrantMutex.Mara Bos-7/+7
2020-09-16Don't use `mut` in Windows Mutex.Mara Bos-9/+7
2020-09-16Sets as_flags as unstableFederico Ponzi-1/+1
2020-09-16Rollup merge of #75749 - ehuss:consolidate-sys, r=alexcrichtonDylan DPC-889/+56
Consolidate some duplicate code in the sys modules. This consolidates some modules which were duplicated throughout the sys module. The intent is to make it easier to update and maintain this code. This mainly affects the wasi, sgx, and "unsupported" targets. I explicitly skipped hermit, cloudabi, and vxworks. These tier-3 targets have copied large sections of the sys tree. I don't think they should have, but I don't want to put effort into changing them. It also doesn't help that there aren't any scripts or instructions for building them. There are still sections of duplicate code here and there, but this PR covers the easy parts where entire modules are the same.
2020-09-15[fuchsia] Propagate the userspace UTC clockAdam Lesinski-1/+3
On Fuchsia, spawning a subprocess does not automatically clone all of the parent process' capabilities. UTC time on Fuchsia is managed by a top-level userspace clock capability that is cloned and passed to subprocesses. This change ensures that any Rust subprocess gets access to the UTC clock, if the parent had access to it. This is critical for tests, which on Fuchsia, use panic=abort and spawn subprocesses per test.
2020-09-15Auto merge of #75148 - joechrisellis:master, r=Amanieubors-0/+185
Implementation of peer credentials for Unix sockets The code in `ucred.rs` is based on the work done in [PR 13](https://github.com/tokio-rs/tokio-uds/pull/13) in the tokio-uds repository on GitHub. This commit is effectively a port to the stdlib, so credit to Martin Habovštiak (`@Kixunil)` and contributors for the meat of this work. 🥇 Happy to make changes as needed. 🙂
2020-09-15Consolidate wasi::process and unsupported::processEric Huss-157/+3
2020-09-15Consolidate wasi alloc with unix alloc.Eric Huss-111/+45
2020-09-15Consolidate byte-identical modules.Eric Huss-621/+8
2020-09-14Auto merge of #76278 - jethrogb:jb/sgx-rwlock-init-test, r=Mark-Simulacrumbors-23/+11
Improve SGX RWLock initializer test r? `@eddyb` This addresses https://github.com/pnkfelix/rust/pull/1#discussion_r374239895 Fixes https://github.com/fortanix/rust-sgx/issues/213
2020-09-14Fix peer credentials for AndroidJoe Ellis-6/+5
2020-09-14Conditionally compile peer credentials feature for supported platformsJoe Ellis-0/+18
2020-09-14Add documentation to public fields of UCred structJoe Ellis-1/+8
2020-09-14Move Unix peer credentials tests to their own fileJoe Ellis-20/+16
2020-09-14Add pid as an option to UCred structJoe Ellis-3/+5
Currently, PID will be populated for Linux, and set to None for BSDs.
2020-09-14Use `u32::MAX` instead of `u32::max_value`Joe Ellis-1/+1
Co-authored-by: lzutao <taolzu@gmail.com>
2020-09-14Add basic test for Unix peer credentialsJoe Ellis-0/+20
2020-09-14Remove use of `MaybeUninit` in `ucred.rs`Joe Ellis-5/+3
We can simply init the struct directly. There is no real need to use uninit memory here.
2020-09-14Implementation of peer credentials for Unix socketsJoe Ellis-0/+145
The code in `ucred.rs` is based on the work done in PR 13 in the tokio-uds repository on GitHub. Link below for reference: https://github.com/tokio-rs/tokio-uds/pull/13 Credit to Martin Habovštiak (GitHub username Kixunil) and contributors for this work!
2020-09-12Remove Windows details from Unix and VmWorks symlink() docstringsNicholas Bishop-18/+0
This note is not relevant to other operating systems.
2020-09-12Small cleanups in Windows Mutex.Mara Bos-32/+32
- Move `held` into the boxed part, since the SRW lock implementation does not use this. This makes the Mutex 50% smaller. - Use `Cell` instead of `UnsafeCell` for `held`, such that `.replace()` can be used. - Add some comments.
2020-09-12Auto merge of #76561 - Thomasdezeeuw:iov-constant-limits, r=Amanieubors-18/+47
Use IOV_MAX and UIO_MAXIOV constants in limit vectored I/O Also updates the libc dependency to 0.2.77 (from 0.2.74) as the constants were only recently added. Related #68042, #75005 r? `@Amanieu` (also reviewed #75005)
2020-09-12Rollup merge of #76583 - CDirkx:os-doc, r=jonas-schievinkRalf Jung-6/+8
Update `std::os` module documentation. Adds missing descriptions for the modules `std::os::linux::fs` and `std::os::windows::io`. Also adds punctuation for consistency with other descriptions.
2020-09-11Ignore unnecessary unsafe warningsThomas de Zeeuw-2/+21
This is a work-around for a libc issue: https://github.com/rust-lang/libc/issues/1888.
2020-09-11Add `peek` and `peek_from` to `UnixStream` and `UnixDatagram`rijenkii-20/+192
2020-09-11Update `std::os` module documentation.Christiaan Dirkx-6/+8
Adds missing descriptions for the modules std::os::linux::fs and std::os::windows::io. Also adds punctuation for consistency with other descriptions.
2020-09-10Use IOV_MAX and UIO_MAXIOV constants in limit vectored I/OThomas de Zeeuw-16/+26
Also updates the libc dependency to 0.2.77 (from 0.2.74) as the constants were only recently added.
2020-09-09Only call pthread_attr_destroy() after getattr_np() succeeds on all libcsTavian Barnes-2/+4
The calling convention of pthread_getattr_np() is to initialize the pthread_attr_t, so _destroy() is only necessary on success (and _init() isn't necessary beforehand). On the other hand, FreeBSD wants the attr_t to be initialized before pthread_attr_get_np(), and therefore it should always be destroyed afterwards.
2020-09-09Fix segfault if pthread_getattr_np failsTavian Barnes-2/+6
glibc destroys[1] the passed pthread_attr_t if pthread_getattr_np() fails. Destroying it again leads to a segfault. Fix it by only destroying it on success for glibc. [1]: https://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/pthread_getattr_np.c;h=ce437205e41dc05653e435f6188768cccdd91c99;hb=HEAD#l205
2020-09-08Capitalize safety commentsFlying-Toast-2/+2
2020-09-07Rollup merge of #76346 - gillespiecd:nlinks-docs, r=Dylan-DPCDylan DPC-2/+2
Docs: nlink example typo Small typo fix for the `nlink` function, extra whitespace before the `use` declaration
2020-09-05Auto merge of #75428 - the8472:fix-copy-eopnotsupp, r=joshtriplettbors-10/+17
Workarounds for copy_file_range issues fixes #75387 fixes #75446
2020-09-04Fix nlink example typoChris Gillespie-2/+2
2020-09-04Add is_enclave_range/is_user_range overflow checksTheodore Cipicchio-8/+34
Functions such as `is_enclave_range` and `is_user_range` in `sgx::os::fortanix_sgx::mem` are often used to make sure memory ranges passed to an enclave from untrusted code or passed to other trusted code functions are safe to use for their intended purpose. Currently, these functions do not perform any checks to make sure the range provided doesn't overflow when adding the range length to the base address. While debug builds will panic if overflow occurs, release builds will simply wrap the result, leading to false positive results for either function. The burden is placed on application authors to know to perform overflow checks on their own before calling these functions, which can easily lead to security vulnerabilities if omitted. Additionally, since such checks are performed in the Intel SGX SDK versions of these functions, developers migrating from Intel SGX SDK code may expect these functions to operate the same. This commit adds explicit overflow checking to `is_enclave_range` and `is_user_range`, returning `false` if overflow occurs in order to prevent misuse of invalid memory ranges. It also alters the checks to account for ranges that lie exactly at the end of the address space, where calculating `p + len` would overflow despite the range being valid.
2020-09-03Improve SGX RWLock initializer testJethro Beekman-23/+11
2020-09-03Auto merge of #76235 - jyn514:std-intra-links, r=poliorceticsbors-2/+5
Convert many files to intra-doc links Helps with https://github.com/rust-lang/rust/issues/75080 r? @poliorcetics I recommend reviewing one commit at a time, but the diff is small enough you can do it all at once if you like :)
2020-09-03Auto merge of #75971 - Amjad50:libstd-deny-unsafe_op_in_unsafe_fn, ↵bors-8/+60
r=Mark-Simulacrum Applied `#![deny(unsafe_op_in_unsafe_fn)]` in library/std/src/wasi partial fix for #73904 There are still more that was not applied in [mod.rs]( https://github.com/rust-lang/rust/blob/38fab2ea92a48980219989817201bf2094ae826a/library/std/src/sys/wasi/mod.rs) and that is due to its using files from `../unsupported` like: ``` #[path = "../unsupported/cmath.rs"] pub mod cmath; ```
2020-09-03Applied `#![deny(unsafe_op_in_unsafe_fn)]` in library/std/src/wasiAmjad Alsharafi-8/+60
All refactoring needed was only in `alloc.rs`, changed part of the code in `alloc` method to satisfy the SAFETY statement
2020-09-02Convert many files to intra-doc linksJoshua Nelson-2/+5
- Use intra-doc links for `std::io` in `std::fs` - Use intra-doc links for File::read in unix/ext/fs.rs - Remove explicit intra-doc links for `true` in `net/addr.rs` - Use intra-doc links in alloc/src/sync.rs - Use intra-doc links in src/ascii.rs - Switch to intra-doc links in alloc/rc.rs - Use intra-doc links in core/pin.rs - Use intra-doc links in std/prelude - Use shorter links in `std/fs.rs` `io` is already in scope.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-02 20:51:09 +0000