DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <mcoqueli@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com,
	 stable@dpdk.org
Subject: Re: [PATCH v2 2/2] vhost: fix uninitialized VQ info in VDUSE vring setup
Date: Wed, 15 Oct 2025 13:44:43 +0200	[thread overview]
Message-ID: <CAO55csz5EY5r5T_ZgjhsfSd5cXLkP5RJACdjpRjU0nrFWBWn1Q@mail.gmail.com> (raw)
In-Reply-To: <20250916093550.1345901-3-maxime.coquelin@redhat.com>

On Tue, Sep 16, 2025 at 11:36 AM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> Initialize vduse_vq_info structure to zero to avoid using
> uninitialized memory when setting up VDUSE virtual rings.
> This ensures all fields start with known values.
>
> Fixes: a9120db8b98b ("vhost: add VDUSE device startup")
> Cc: stable@dpdk.org
>
> Reported-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
Applied to next-virtio/for-next-net.

Thanks,
Maxime


  parent reply	other threads:[~2025-10-15 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  9:35 [PATCH v2 0/2] vhost: VDUSE startup workaround and fix Maxime Coquelin
2025-09-16  9:35 ` [PATCH v2 1/2] vhost: add VDUSE virtqueue ready state polling workaround Maxime Coquelin
2025-10-15 11:44   ` Maxime Coquelin
2025-09-16  9:35 ` [PATCH v2 2/2] vhost: fix uninitialized VQ info in VDUSE vring setup Maxime Coquelin
2025-10-01  8:43   ` David Marchand
2025-10-15 11:44   ` Maxime Coquelin [this message]
2025-09-16 13:09 ` [PATCH v2 0/2] vhost: VDUSE startup workaround and fix Patrick Robb

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=CAO55csz5EY5r5T_ZgjhsfSd5cXLkP5RJACdjpRjU0nrFWBWn1Q@mail.gmail.com \
    --to=mcoqueli@redhat.com \
    --cc=chenbox@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=stable@dpdk.org \
    /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).