patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: David Marchand <david.marchand@redhat.com>
Cc: stable@dpdk.org
Subject: Re: [PATCH 22.11] vhost: fix virtqueue access check in vhost-user setup
Date: Thu, 7 Mar 2024 12:45:33 +0000	[thread overview]
Message-ID: <CAMw=ZnTHzpcgfvbNJwzDQtCJ_eSNQzj505Z7_P0MRM9qKDiKjw@mail.gmail.com> (raw)
In-Reply-To: <20240307080604.4028280-1-david.marchand@redhat.com>

On Thu, 7 Mar 2024 at 08:06, David Marchand <david.marchand@redhat.com> wrote:
>
> [ upstream commit b3e42d92362bcc75df21c5b86ba7c0685b40a3bf ]
>
> Calling vring_invalidate must be done with a (write) lock taken on the
> virtqueue.
>
> Fixes: 72d002b3ebda ("vhost: fix vring address handling during live migration")
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Acked-by: Eelco Chaudron <echaudro@redhat.com>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
>  lib/vhost/vhost_user.c | 2 ++
>  1 file changed, 2 insertions(+)

Thanks, applied

      reply	other threads:[~2024-03-07 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  8:06 David Marchand
2024-03-07 12:45 ` Luca Boccassi [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='CAMw=ZnTHzpcgfvbNJwzDQtCJ_eSNQzj505Z7_P0MRM9qKDiKjw@mail.gmail.com' \
    --to=bluca@debian.org \
    --cc=david.marchand@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).