Re-enable armv7-sony-vita-newlibeabihf in CI. (#1408)

Re-enable armv7-sony-vita-newlibeabihf cross check in CI. Also, add a
few comments.

Author: sunfishcode

.github/workflows/main.yml

@@ -226,8 +226,7 @@ jobs:
     - run: cargo check -Z build-std --target=aarch64-unknown-nto-qnx710 --features=all-apis
     - run: cargo check -Z build-std --target=x86_64-pc-nto-qnx710 --features=all-apis
     - run: cargo check -Z build-std --target=armv6k-nintendo-3ds --all-features
-    # Temporarily disable armv7-sony-vita-newlibeabihf, as it gets build errors.
-    # - run: cargo check -Z build-std --target=armv7-sony-vita-newlibeabihf --features=all-apis
+    - run: cargo check -Z build-std --target=armv7-sony-vita-newlibeabihf --features=all-apis
     - run: cargo check -Z build-std --target=powerpc64-ibm-aix --features=all-apis
     - run: cargo check -Z build-std --target=mipsel-unknown-linux-gnu --features=all-apis
     - run: cargo check -Z build-std --target=mips64el-unknown-linux-gnuabi64 --features=all-apis

src/buffer.rs

@@ -93,7 +93,7 @@ use core::slice;
 /// If you see errors like
 /// "captured variable cannot escape `FnMut` closure body",
 /// use an explicit loop instead of `retry_on_intr`, assuming you're using
-/// that. See `error_retry_closure_uninit` in examples.rs.
+/// that. See `error_retry_closure_uninit` in examples/buffer_errors.rs.
 pub trait Buffer<T>: private::Sealed<T> {}
 
 // Implement `Buffer` for all the types that implement `Sealed`.

src/ioctl/mod.rs

@@ -65,6 +65,10 @@ use bsd as platform;
 /// drivers in the kernel, and safety depends on both sides agreeing and
 /// upholding the expectations of the other.
 ///
+/// And, `ioctl` calls can read and write arbitrary memory and have arbitrary
+/// side effects. Callers must ensure that any memory accesses and side effects
+/// are compatible with Rust language invariants.
+///
 /// # References
 ///  - [Linux]
 ///  - [Winsock]

src/rand/getrandom.rs

@@ -12,8 +12,13 @@ pub use backend::rand::types::GetRandomFlags;
 /// This is a very low-level API which may be difficult to use correctly. Most
 /// users should prefer to use [`getrandom`] or [`rand`] APIs instead.
 ///
+/// This function is implemented using a system call, and not the
+/// [vDSO mechanism] introduced in Linux 6.11. See [#1185] for details.
+///
 /// [`getrandom`]: https://crates.io/crates/getrandom
 /// [`rand`]: https://crates.io/crates/rand
+/// [vDSO mechanism]: https://lwn.net/Articles/983186/
+/// [#1185]: https://github.com/bytecodealliance/rustix/issues/1185
 ///
 /// # References
 ///  - [Linux]

src/runtime.rs

@@ -29,7 +29,14 @@
 //! program or what they're doing, but the features in this module generally
 //! can only be used by one entity within a process.
 //!
+//! All that said, there are some functions in this module would could
+//! potentially be stabilized and moved to other modules. See also the
+//! documentation for specific functions in the [`not_implemented`] module, and
+//! the discussion in [#1314].
+//!
 //! [Origin]: https://github.com/sunfishcode/origin#readme
+//! [`not_implemented`]: crate::not_implemented
+//! [#1314]: https://github.com/bytecodealliance/rustix/issues/1314
 //!
 //! # Safety
 //!