From: Jon Maloy <jmaloy@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v8 2/3] iov: Introduce IOV_PUSH_HEADER() macro
Date: Sat, 9 May 2026 18:15:57 -0400 [thread overview]
Message-ID: <139d4189-f5d7-4bc1-97ec-43ca938ab61b@redhat.com> (raw)
In-Reply-To: <20260416160926.3822963-3-lvivier@redhat.com>
On 2026-04-16 12:09, Laurent Vivier wrote:
> Add iov_push_header_() and its typed wrapper IOV_PUSH_HEADER() to write
> a header into an iov_tail at the current offset and advance past it.
>
> This is the write counterpart to IOV_PEEK_HEADER() / IOV_REMOVE_HEADER(),
> using iov_from_buf() to copy the header data across iovec boundaries.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> iov.c | 23 +++++++++++++++++++++++
> iov.h | 11 +++++++++++
> 2 files changed, 34 insertions(+)
>
> diff --git a/iov.c b/iov.c
> index 28c6d40d2986..b1bcdc4649df 100644
> --- a/iov.c
> +++ b/iov.c
> @@ -360,6 +360,29 @@ void *iov_peek_header_(struct iov_tail *tail, void *v, size_t len, size_t align)
> return v;
> }
>
> +/**
> + * iov_push_header_() - Write a new header to an IOV tail
> + * @tail: IOV tail to write header to
> + * @v: Pointer to header data to write
> + * @len: Length of header to write, in bytes
> + *
> + * Return: number of bytes written
> + */
> +/* cppcheck-suppress unusedFunction */
> +size_t iov_push_header_(struct iov_tail *tail, const void *v, size_t len)
> +{
> + size_t l;
> +
> + if (!iov_tail_prune(tail))
> + return 0; /* No space */
> +
> + l = iov_from_buf(tail->iov, tail->cnt, tail->off, v, len);
> +
> + tail->off = tail->off + l;
> +
> + return l;
> +}
A small observation: if iov_from_buf() returns less than ´len' because
the tail has insufficient space, this function advances tail->off by
that lenght and returns it. The caller in IOV_PUSH_HEADER gets back a
(value != sizeof(header)), but ignores it. This means a partial header
write would go undetected.
Maybe a warning or even an assert() would be in place here?
/jon
> +
> /**
> * iov_remove_header_() - Remove a header from an IOV tail
> * @tail: IOV tail to remove header from (modified)
> diff --git a/iov.h b/iov.h
> index 3c63308e554f..4fdf14a85b19 100644
> --- a/iov.h
> +++ b/iov.h
> @@ -93,6 +93,7 @@ bool iov_tail_prune(struct iov_tail *tail);
> size_t iov_tail_size(struct iov_tail *tail);
> bool iov_drop_header(struct iov_tail *tail, size_t len);
> void *iov_peek_header_(struct iov_tail *tail, void *v, size_t len, size_t align);
> +size_t iov_push_header_(struct iov_tail *tail, const void *v, size_t len);
> void *iov_remove_header_(struct iov_tail *tail, void *v, size_t len, size_t align);
> ssize_t iov_tail_clone(struct iovec *dst_iov, size_t dst_iov_cnt,
> struct iov_tail *tail);
> @@ -115,6 +116,16 @@ ssize_t iov_tail_clone(struct iovec *dst_iov, size_t dst_iov_cnt,
> sizeof(var_), \
> __alignof__(var_))))
>
> +/**
> + * IOV_PUSH_HEADER() - Write a new header to an IOV tail
> + * @tail_: IOV tail to write header to
> + * @var_: A variable containing the header data to write
> + *
> + * Return: number of bytes written
> + */
> +#define IOV_PUSH_HEADER(tail_, var_) \
> + (iov_push_header_((tail_), &(var_), sizeof(var_)))
> +
> /**
> * IOV_REMOVE_HEADER() - Remove and return typed header from an IOV tail
> * @tail_: IOV tail to remove header from (modified)
next prev parent reply other threads:[~2026-05-09 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 16:09 [PATCH v8 0/3] vhost-user,udp: Handle multiple iovec entries per virtqueue element Laurent Vivier
2026-04-16 16:09 ` [PATCH v8 1/3] udp_vu: Allow virtqueue elements with multiple iovec entries Laurent Vivier
2026-05-09 21:02 ` Jon Maloy
2026-04-16 16:09 ` [PATCH v8 2/3] iov: Introduce IOV_PUSH_HEADER() macro Laurent Vivier
2026-05-09 22:15 ` Jon Maloy [this message]
2026-04-16 16:09 ` [PATCH v8 3/3] udp: Pass iov_tail to udp_update_hdr4()/udp_update_hdr6() Laurent Vivier
2026-05-09 22:27 ` Jon Maloy
2026-05-11 2:42 ` 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=139d4189-f5d7-4bc1-97ec-43ca938ab61b@redhat.com \
--to=jmaloy@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).