From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by passt.top (Postfix, from userid 1000) id 801F25A0620; Mon, 03 Nov 2025 11:16:29 +0100 (CET) From: Stefano Brivio To: passt-dev@passt.top, Laurent Vivier Subject: [RFC PATCH 0/3] Fill exceeding size of vhost-user buffers explicitly Date: Mon, 3 Nov 2025 11:16:26 +0100 Message-ID: <20251103101629.1412331-1-sbrivio@redhat.com> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID-Hash: ZPGMR44P325IGW7HQH4PZVW4VYO4A7CB X-Message-ID-Hash: ZPGMR44P325IGW7HQH4PZVW4VYO4A7CB X-MailFrom: sbrivio@passt.top X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: David Gibson X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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