qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Cave-Ayland <mark.caveayland@nutanix.com>
To: John Levon <john.levon@nutanix.com>, qemu-devel@nongnu.org
Cc: "Thanos Makatos" <thanos.makatos@nutanix.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH v3 5/5] vfio-user: recycle msg on failure
Date: Tue, 2 Dec 2025 11:14:38 +0000	[thread overview]
Message-ID: <865e73ba-ecc6-4b3a-a4b3-ea17860cd3a9@nutanix.com> (raw)
In-Reply-To: <20251201095621.2786318-6-john.levon@nutanix.com>

On 01/12/2025 09:56, John Levon wrote:

> If we fail to read an incoming request, recycle the message.
> 
> Resolves: Coverity CID 1611807
> Resolves: Coverity CID 1611808
> Signed-off-by: John Levon <john.levon@nutanix.com>
> ---
>   hw/vfio-user/proxy.c | 21 ++++++++++++++++-----
>   1 file changed, 16 insertions(+), 5 deletions(-)
> 
> diff --git a/hw/vfio-user/proxy.c b/hw/vfio-user/proxy.c
> index d1d63816b3..d06978a74f 100644
> --- a/hw/vfio-user/proxy.c
> +++ b/hw/vfio-user/proxy.c
> @@ -412,11 +412,22 @@ err:
>       for (i = 0; i < numfds; i++) {
>           close(fdp[i]);
>       }
> -    if (isreply && msg != NULL) {
> -        /* force an error to keep sending thread from hanging */
> -        vfio_user_set_error(msg->hdr, EINVAL);
> -        msg->complete = true;
> -        qemu_cond_signal(&msg->cv);
> +    if (msg != NULL) {
> +        if (msg->type == VFIO_MSG_REQ) {
> +            /*
> +             * Clean up the request message on failure. Change type back to
> +             * NOWAIT to free.
> +             */
> +            msg->type = VFIO_MSG_NOWAIT;
> +            vfio_user_recycle(proxy, msg);
> +        } else {
> +            /*
> +             * Report an error back to the sender. Sender will recycle msg.
> +             */
> +            vfio_user_set_error(msg->hdr, EINVAL);
> +            msg->complete = true;
> +            qemu_cond_signal(&msg->cv);
> +        }
>       }
>       return -1;
>   }

Reviewed-by: Mark Cave-Ayland <mark.caveayland@nutanix.com>


ATB,

Mark.



      reply	other threads:[~2025-12-02 11:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-01  9:56 [PATCH v3 0/5] vfio-user coverity fixes John Levon
2025-12-01  9:56 ` [PATCH v3 1/5] vfio-user: simplify vfio_user_process() John Levon
2025-12-02 10:42   ` Mark Cave-Ayland
2025-12-01  9:56 ` [PATCH v3 2/5] vfio-user: clarify partial message handling John Levon
2025-12-02 10:43   ` Mark Cave-Ayland
2025-12-01  9:56 ` [PATCH v3 3/5] vfio-user: refactor out header handling John Levon
2025-12-02 10:53   ` Mark Cave-Ayland
2025-12-03  7:40     ` Cédric Le Goater
2025-12-01  9:56 ` [PATCH v3 4/5] vfio-user: simplify vfio_user_recv_one() John Levon
2025-12-02 11:11   ` Mark Cave-Ayland
2025-12-01  9:56 ` [PATCH v3 5/5] vfio-user: recycle msg on failure John Levon
2025-12-02 11:14   ` Mark Cave-Ayland [this message]

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=865e73ba-ecc6-4b3a-a4b3-ea17860cd3a9@nutanix.com \
    --to=mark.caveayland@nutanix.com \
    --cc=clg@redhat.com \
    --cc=john.levon@nutanix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thanos.makatos@nutanix.com \
    /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.
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 NNTP newsgroup(s).