From: Eugenio Perez Martin <eperezma@redhat.com>
To: mjt@tls.msk.ru
Cc: qemu-devel@nongnu.org, Cindy Lu <lulu@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Lei Yang <leiyang@redhat.com>, Jason Wang <jasowang@redhat.com>,
Hawkins Jiawei <yin31149@gmail.com>
Subject: Re: [PATCH] vdpa: fix not using CVQ buffer in case of error
Date: Wed, 7 Jun 2023 15:52:49 +0200 [thread overview]
Message-ID: <CAJaqyWeAsSJBhDtGkGTuf+uQsaEMOsNYMzhbwkJ6yAJ1-q+9pA@mail.gmail.com> (raw)
In-Reply-To: <47527a58-039e-55e7-3541-bcd7ceb3296a@tls.msk.ru>
On Wed, Jun 7, 2023 at 12:11 PM Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> 02.06.2023 20:34, Eugenio Pérez wrote:
> > Bug introducing when refactoring. Otherway, the guest never received
> > the used buffer.
> >
> > Fixes: be4278b65fc1 ("vdpa: extract vhost_vdpa_net_cvq_add from vhost_vdpa_net_handle_ctrl_avail")
> > Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
> > ---
> > net/vhost-vdpa.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Again, smells like a stable material, is it not?
>
> Please Cc: qemu-stable@nongnu.org for other changes you think should be
> applied to stable qemu series.
>
Sorry, I totally forgot. This one should go to stable, yes.
Thanks!
next prev parent reply other threads:[~2023-06-07 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 17:34 [PATCH] vdpa: fix not using CVQ buffer in case of error Eugenio Pérez
2023-06-06 1:32 ` Jason Wang
2023-06-07 8:18 ` Lei Yang
2023-06-07 10:10 ` Michael Tokarev
2023-06-07 13:52 ` Eugenio Perez Martin [this message]
2023-06-07 16:04 ` Michael Tokarev
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=CAJaqyWeAsSJBhDtGkGTuf+uQsaEMOsNYMzhbwkJ6yAJ1-q+9pA@mail.gmail.com \
--to=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=leiyang@redhat.com \
--cc=lulu@redhat.com \
--cc=lvivier@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yin31149@gmail.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).