From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [RFC PATCH 0/3] Fill exceeding size of vhost-user buffers explicitly
Date: Mon, 3 Nov 2025 11:16:26 +0100 [thread overview]
Message-ID: <20251103101629.1412331-1-sbrivio@redhat.com> (raw)
While looking for a way to ensure inbound frames are padded to 60 bytes
in vhost-user mode, I spotted the issue described in 1/3, which looks a
bit too obvious to be true, so I'm sending this as RFC.
Am I missing something there, or do we actually need to fix that?
Stefano Brivio (3):
vu_common: Stick to size of input buffer in vu_send_single()
iov: Fix coding style of basic (non-IOV_TAIL) parts
iov, vu_common: Make iov_from_buf() fill destination iov entirely
iov.c | 116 +++++++++++++++++++++++++++-------------------------
iov.h | 4 +-
vu_common.c | 22 +++++-----
3 files changed, 74 insertions(+), 68 deletions(-)
--
2.43.0
next reply other threads:[~2025-11-03 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 10:16 Stefano Brivio [this message]
2025-11-03 10:16 ` [RFC PATCH 1/3] vu_common: Stick to size of input buffer in vu_send_single() Stefano Brivio
2025-11-04 15:01 ` Laurent Vivier
2025-11-04 16:09 ` Stefano Brivio
2025-11-04 16:24 ` Laurent Vivier
2025-11-03 10:16 ` [RFC PATCH 2/3] iov: Fix coding style of basic (non-IOV_TAIL) parts Stefano Brivio
2025-11-04 15:14 ` Laurent Vivier
2025-11-05 3:58 ` David Gibson
2025-11-03 10:16 ` [RFC PATCH 3/3] iov, vu_common: Make iov_from_buf() fill destination iov entirely Stefano Brivio
2025-11-04 15:11 ` Laurent Vivier
2025-11-05 4:01 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251103101629.1412331-1-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).