vsock: fix minor typos

Signed-off-by: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
This commit is contained in:
Manos Pitsidianakis 2025-07-02 14:57:09 +03:00 committed by Manos Pitsidianakis
parent 7dae694e63
commit 79a8bc683d
3 changed files with 3 additions and 3 deletions

View File

@ -177,7 +177,7 @@ guest$ nc --vsock 2 1234
If you add multiple VMs with their devices configured with at least one common group name, they can communicate with
each other. If you don't explicitly specify a group name, a default group will be assigned to the device with name
`default`, and all such devices will be able to communicate with each other. Or you can choose a different list of
group names for each device, and only devices with the at least one group in commmon will be able to communicate with
group names for each device, and only devices with the at least one group in common will be able to communicate with
each other.
For example, if you have two VMs with CID 3 and 4, you can run the following commands to make them communicate:

View File

@ -210,7 +210,7 @@ pub(crate) struct VsockThreadBackend {
tx_buffer_size: u32,
/// Maps the guest CID to the corresponding backend. Used for sibling VM communication.
pub cid_map: Arc<RwLock<CidMap>>,
/// Queue of raw vsock packets recieved from sibling VMs to be sent to the guest.
/// Queue of raw vsock packets received from sibling VMs to be sent to the guest.
pub raw_pkts_queue: Arc<RwLock<RawPktsQ>>,
/// Set of groups assigned to the device which it is allowed to communicate with.
groups_set: Arc<RwLock<HashSet<String>>>,

View File

@ -57,7 +57,7 @@ impl LocalTxBuf {
let remain_txbuf = &mut self.buf[..(data_buf.len() - len)];
data_buf
.read_slice(remain_txbuf, len)
.expect("shouldn't faile because remain_txbuf's len is data_buf.len() - len");
.expect("shouldn't fail because remain_txbuf's len is data_buf.len() - len");
}
// Increment tail by the amount of data that has been added to the buffer