Comment out io_uring_enter_reg_wait for now. (#1376)

Also, fix several typos in comments.

Author: sunfishcode

src/backend/libc/net/addr.rs

@@ -161,7 +161,7 @@ impl SocketAddrUnix {
         owned.extend_from_slice(bytes);
         owned.push(b'\0');
         // SAFETY: `from_vec_with_nul_unchecked` since the string is
-        // NUL-terminated and `bytes` does not conain any NULs.
+        // NUL-terminated and `bytes` does not contain any NULs.
         Some(Cow::Owned(
             CString::from_vec_with_nul_unchecked(owned).into(),
         ))

src/backend/linux_raw/net/addr.rs

@@ -123,7 +123,7 @@ impl SocketAddrUnix {
         owned.extend_from_slice(bytes);
         owned.push(b'\0');
         // SAFETY: `from_vec_with_nul_unchecked` since the string is
-        // NUL-terminated and `bytes` does not conain any NULs.
+        // NUL-terminated and `bytes` does not contain any NULs.
         Some(Cow::Owned(
             CString::from_vec_with_nul_unchecked(owned).into(),
         ))

src/event/select.rs

@@ -232,7 +232,7 @@ pub fn fd_set_num_elements(set_count: usize, nfds: RawFd) -> usize {
 #[cfg(any(windows, target_os = "wasi"))]
 #[inline]
 pub(crate) fn fd_set_num_elements_for_fd_array(set_count: usize) -> usize {
-    // Ensure that we always have a big enough set to derefence an `FD_SET`.
+    // Ensure that we always have a big enough set to dereference an `FD_SET`.
     core::cmp::max(
         fd_set_num_elements_for_fd_array_raw(set_count),
         div_ceil(size_of::<FD_SET>(), size_of::<FdSetElement>()),

src/io_uring/mod.rs

@@ -271,9 +271,11 @@ pub unsafe fn io_uring_enter_arg<Fd: AsFd>(
     )
 }
 
+// TODO: Uncomment this when we support `IoringRegisterOp::CQWAIT_REG`.
+/*
 /// `io_uring_enter2(fd, to_submit, min_complete, flags, offset,
 /// sizeof(io_uring_reg_wait))`— Initiate and/or complete asynchronous I/O,
-/// using a previously regisered `io_uring_reg_wait`.
+/// using a previously registered `io_uring_reg_wait`.
 ///
 /// `offset` is an offset into an area of wait regions previously registered
 /// with [`io_uring_register`] using the [`IoringRegisterOp::CQWAIT_REG`]
@@ -314,6 +316,7 @@ pub unsafe fn io_uring_enter_reg_wait<Fd: AsFd>(
         size_of::<io_uring_reg_wait>(),
     )
 }
+*/
 
 bitflags::bitflags! {
     /// `IORING_ENTER_*` flags for use with [`io_uring_enter`].

src/kernel_sigset.rs

@@ -11,7 +11,7 @@ use linux_raw_sys::general::{kernel_sigset_t, _NSIG};
 /// `kernel_sigset_t`—A set of signal numbers, as used by some syscalls.
 ///
 /// This is similar to `libc::sigset_t`, but with only enough space for the
-/// signals currently known to be used by the kernel. libc implementaions
+/// signals currently known to be used by the kernel. libc implementations
 /// reserve extra space so that if Linux defines new signals in the future
 /// they can add support without breaking their dynamic linking ABI. Rustix
 /// doesn't support a dynamic linking ABI, so if we need to increase the

src/runtime.rs

@@ -536,7 +536,7 @@ pub unsafe fn kernel_sigaction(
 /// While the memory region pointed to by `new` is registered as a signal
 /// stack, it must remain readable and writable, and must not be mutated in
 /// any way other than by having a signal handler run in it, and must not be
-/// the referant of a Rust reference from outside the signal handler.
+/// the referent of a Rust reference from outside the signal handler.
 ///
 /// If code elsewhere in the program is depending on signal handlers being run
 /// on a particular stack, this could break that code's assumptions. And if the