ch: Fix various misspelled words

Misspellings were identified by https://github.com/marketplace/actions/check-spelling
* Initial corrections suggested by Google Sheets
* Additional corrections by Google Chrome auto-suggest
* Some manual corrections

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
This commit is contained in:
Josh Soref
2020-09-22 07:31:42 -04:00
committed by Rob Bradford
parent 22a2a99e5f
commit 5c3f4dbe6f
32 changed files with 56 additions and 56 deletions

View File

@@ -809,7 +809,7 @@ impl Iommu {
// virtual IOMMU. This list is translated into a virtio-iommu configuration
// topology, so that it can be understood by the guest driver.
//
// The topology is overriden everytime this function is being invoked.
// The topology is overridden everytime this function is being invoked.
//
// This function is dedicated to PCI, which means it will exclusively
// create VIRTIO_IOMMU_TOPO_PCI_RANGE entries.

View File

@@ -66,7 +66,7 @@ const VIRTIO_MEM_RESP_NACK: u16 = 1;
// - VIRTIO_MEM_REQ_UNPLUG_ALL
// VIRTIO_MEM_RESP_BUSY: u16 = 2;
// Error in request (e.g. addresses/alignemnt), applicable for
// Error in request (e.g. addresses/alignment), applicable for
// - VIRTIO_MEM_REQ_PLUG
// - VIRTIO_MEM_REQ_UNPLUG
// - VIRTIO_MEM_REQ_STATE
@@ -664,7 +664,7 @@ impl EpollHelperHandler for MemEpollHandler {
},
};
if let Err(e) = self.resize.send(r) {
error!("Sending \"resize\" reponse: {:?}", e);
error!("Sending \"resize\" response: {:?}", e);
return true;
}
if signal_error {

View File

@@ -82,7 +82,7 @@ pub enum Error {
InvalidQueuePairsNum,
/// No memory passed in.
NoMemory,
/// No ueue pairs nummber.
/// No ueue pairs number.
NoQueuePairsNum,
}

View File

@@ -235,7 +235,7 @@ where
}
Err(err) if err.kind() == ErrorKind::WouldBlock => {
// This shouldn't actually happen (receiving EWOULDBLOCK after EPOLLIN), but
// apparently it does, so we need to handle it greacefully.
// apparently it does, so we need to handle it gracefully.
warn!(
"vsock: unexpected EWOULDBLOCK while reading from backing stream: \
lp={}, pp={}, err={:?}",
@@ -905,7 +905,7 @@ mod tests {
let mut ctx = CsmTestContext::new(ConnState::PeerInit);
assert!(ctx.conn.has_pending_rx());
ctx.recv();
// For peer-initiated requests, our connection should always yield a vsock reponse packet,
// For peer-initiated requests, our connection should always yield a vsock response packet,
// in order to establish the connection.
assert_eq!(ctx.pkt.op(), uapi::VSOCK_OP_RESPONSE);
assert_eq!(ctx.pkt.src_cid(), LOCAL_CID);
@@ -1165,7 +1165,7 @@ mod tests {
.contains(epoll::Events::EPOLLOUT));
assert_eq!(ctx.conn.tx_buf.len(), data.len());
// Unlock the write stream and notify the connection it can now write its bufferred
// Unlock the write stream and notify the connection it can now write its buffered
// data.
ctx.set_stream(TestStream::new());
ctx.conn.notify(epoll::Events::EPOLLOUT);

View File

@@ -65,7 +65,7 @@ impl TxBuf {
let data = self.data.get_or_insert_with(||
// Using uninitialized memory here is quite safe, since we never read from any
// area of the buffer before writing to it. First we push, then we flush only
// what had been prviously pushed.
// what had been previously pushed.
Box::new(unsafe {mem::MaybeUninit::<[u8; Self::SIZE]>::uninit().assume_init()}));
// Buffer head, as an offset into the data slice.

View File

@@ -19,7 +19,7 @@ use crate::{
};
use anyhow::anyhow;
/// This is the `VirtioDevice` implementation for our vsock device. It handles the virtio-level
/// device logic: feature negociation, device configuration, and device activation.
/// device logic: feature negotiation, device configuration, and device activation.
/// The run-time device logic (i.e. event-driven data handling) is implemented by
/// `super::epoll_handler::EpollHandler`.
///
@@ -272,7 +272,7 @@ where
// After the backend has been kicked, it might've freed up some resources, so we
// can attempt to send it more data to process.
// In particular, if `self.backend.send_pkt()` halted the TX queue processing (by
// reurning an error) at some point in the past, now is the time to try walking the
// returning an error) at some point in the past, now is the time to try walking the
// TX queue again.
if let Err(e) = self.process_tx() {
error!("Failed to process TX queue: {:?}", e);

View File

@@ -70,7 +70,7 @@ const HDROFF_TYPE: usize = 28;
// Operation ID - one of the VSOCK_OP_* values; e.g.
// - VSOCK_OP_RW: a data packet;
// - VSOCK_OP_REQUEST: connection request;
// - VSOCK_OP_RST: forcefull connection termination;
// - VSOCK_OP_RST: forceful connection termination;
// etc (see `super::defs::uapi` for the full list).
const HDROFF_OP: usize = 30;

View File

@@ -120,7 +120,7 @@ pub struct VsockMuxer {
impl VsockChannel for VsockMuxer {
/// Deliver a vsock packet to the guest vsock driver.
///
/// Retuns:
/// Returns:
/// - `Ok(())`: `pkt` has been successfully filled in; or
/// - `Err(VsockError::NoData)`: there was no available data with which to fill in the
/// packet.
@@ -280,13 +280,13 @@ impl VsockEpollListener for VsockMuxer {
/// Get the epoll events to be polled upstream.
///
/// Since the polled FD is a nested epoll FD, we're only interested in EPOLLIN events (i.e.
/// some event occured on one of the FDs registered under our epoll FD).
/// some event occurred on one of the FDs registered under our epoll FD).
///
fn get_polled_evset(&self) -> epoll::Events {
epoll::Events::EPOLLIN
}
/// Notify the muxer about a pending event having occured under its nested epoll FD.
/// Notify the muxer about a pending event having occurred under its nested epoll FD.
///
fn notify(&mut self, _: epoll::Events) {
debug!("vsock: muxer received kick");
@@ -376,7 +376,7 @@ impl VsockMuxer {
let key_copy = *key;
let evset_copy = *evset;
// The handling of this event will most probably mutate the state of the
// receiving conection. We'll need to check for new pending RX, event set
// receiving connection. We'll need to check for new pending RX, event set
// mutation, and all that, so we're wrapping the event delivery inside those
// checks.
self.apply_conn_mutation(key_copy, |conn| {
@@ -608,7 +608,7 @@ impl VsockMuxer {
///
fn allocate_local_port(&mut self) -> u32 {
// TODO: this doesn't seem very space-efficient.
// Mybe rewrite this to limit port range and use a bitmap?
// Maybe rewrite this to limit port range and use a bitmap?
//
loop {
@@ -626,10 +626,10 @@ impl VsockMuxer {
self.local_port_set.remove(&port);
}
/// Handle a new connection request comming from our peer (the guest vsock driver).
/// Handle a new connection request coming from our peer (the guest vsock driver).
///
/// This will attempt to connect to a host-side Unix socket, expected to be listening at
/// the file system path corresponing to the destination port. If successful, a new
/// the file system path corresponding to the destination port. If successful, a new
/// connection object will be created and added to the connection pool. On failure, a new
/// RST packet will be scheduled for delivery to the guest.
///
@@ -1232,7 +1232,7 @@ mod tests {
streams.push(listener.accept());
}
// The muxer RX queue should now be full (with connection reponses), but still
// The muxer RX queue should now be full (with connection responses), but still
// synchronized.
assert!(ctx.muxer.rxq.is_synced());