rust/library/std/src/os/linux, branch try

Update version placeholders

2025-07-01T17:54:33+00:00

Rollup merge of #129121 - devnexen:stabilize_ext_linux_tcp_layer, r=tgross35

2025-06-09T11:55:32+00:00

Stabilize `tcp_quickack` to stabilise the quickack part for now, tcp_deferaccept had been added at a later stage. The related API calls are the following ```rust // std::os::linux::net // sealed trait, implemented for std::net::TcpStream pub trait TcpStreamExt: Sealed{ fn quickack(&self) -> io::Result; fn set_quickack(&self, quickack: bool) -> io::Result<()>; } ``` Closes: https://github.com/rust-lang/rust/issues/96256

Add new Tier-3 targets: `loongarch32-unknown-none*`

2025-06-06T00:19:38+00:00

MCP: https://github.com/rust-lang/compiler-team/issues/865

proposal to expand (a subset of) linux specific socket capabilities.

2024-08-15T12:40:55+00:00

to stabilise the quickack part for now, tcp_deferaccept had been added at a later stage.

Reformat `use` declarations.

2024-07-28T22:26:52+00:00

The previous commit updated `rustfmt.toml` appropriately. This commit is the outcome of running `x fmt --all` with the new formatting options.

to extract a pidfd we must consume the child

2024-06-21T22:46:55+00:00

As long as a pidfd is on a child it can be safely reaped. Taking it would mean the child would now have to be awaited through its pid, but could also be awaited through the pidfd. This could then suffer from a recycling race.

Add PidFd::{kill, wait, try_wait}

2024-06-21T22:46:55+00:00

Promote `arm64ec-pc-windows-msvc` to tier 2

2024-06-05T18:37:21+00:00

Convert `Unix{Datagram,Stream}::{set_}passcred()` to per-OS traits

2023-10-25T08:01:21+00:00

These methods are the pre-stabilized API for obtaining peer credentials from an `AF_UNIX` socket, part of the `unix_socket_ancillary_data` feature. Their current behavior is to get/set one of the `SO_PASSCRED` (Linux), `LOCAL_CREDS_PERSISTENT` (FreeBSD), or `LOCAL_CREDS` (NetBSD) socket options. On other targets the `{set_}passcred()` methods do not exist. There are two problems with this approach: 1. Having public methods only exist for certain targets isn't permitted in a stable `std` API. 2. These options have generally similar purposes, but they are non-POSIX and their details can differ in subtle and surprising ways (such as whether they continue to be set after the next call to `recvmsg()`). Splitting into OS-specific extension traits is the preferred solution to both problems.

Finishing clone3 clean up

2024-01-24T14:23:51+00:00