DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbo.xia@outlook.com, fengli@smartx.com
Subject: Re: [PATCH v2 0/7] vhost: ensure virtqueue access status is checked
Date: Wed, 25 Oct 2023 13:40:39 +0200	[thread overview]
Message-ID: <CAJFAV8x0S8pP6hYvkqy2ru2smW1+EckQNrM8miv5dGY0S11w+w@mail.gmail.com> (raw)
In-Reply-To: <20231020084804.3625099-1-maxime.coquelin@redhat.com>

On Fri, Oct 20, 2023 at 10:48 AM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> Li Feng initially reported segmentation fault in rte_vhost_vring_call()
> because of not checking the virtqueue metadata can be accessed.
>
> This should be achieved by checking the access_ok status field of
> the virtqueue.
>
> This series also takes the opportunity to fix the other APIs.
> This is split in multiple patches to ease LTS maintainers backports,
> but could be squashed if preferred.
>
> Changes in v2:
> --------------
> - Rebased to apply on -rc1 (David)
> - Add Fixes tag in patch 1 (David)
> - Fix various typos in commit logs (David)
>
> Maxime Coquelin (7):
>   vhost: fix missing vring call check on virtqueue access
>   vhost: fix missing check on virtqueue access
>   vhost: fix checking virtqueue access when notifying guest
>   vhost: fix check on virtqueue access in async registration
>   vhost: fix check on virtqueue access in in-flight getter
>   vhost: fix missing lock protection in power monitor API
>   vhost: fix checking virtqueue access in stats API
>
>  lib/vhost/vhost.c | 92 +++++++++++++++++++++++++++++++++++++++++++----
>  1 file changed, 85 insertions(+), 7 deletions(-)

For the series,
Acked-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


  parent reply	other threads:[~2023-10-25 11:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20  8:47 Maxime Coquelin
2023-10-20  8:47 ` [PATCH v2 1/7] vhost: fix missing vring call check on virtqueue access Maxime Coquelin
2023-10-20  8:47 ` [PATCH v2 2/7] vhost: fix missing " Maxime Coquelin
2023-10-20  8:48 ` [PATCH v2 3/7] vhost: fix checking virtqueue access when notifying guest Maxime Coquelin
2023-10-20  8:48 ` [PATCH v2 4/7] vhost: fix check on virtqueue access in async registration Maxime Coquelin
2023-10-20  8:48 ` [PATCH v2 5/7] vhost: fix check on virtqueue access in in-flight getter Maxime Coquelin
2023-10-20  8:48 ` [PATCH v2 6/7] vhost: fix missing lock protection in power monitor API Maxime Coquelin
2023-10-20  8:48 ` [PATCH v2 7/7] vhost: fix checking virtqueue access in stats API Maxime Coquelin
2023-10-23 10:01 ` [PATCH v2 0/7] vhost: ensure virtqueue access status is checked David Marchand
2023-10-25 11:40 ` David Marchand [this message]
2023-10-25 12:22 ` Maxime Coquelin

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=CAJFAV8x0S8pP6hYvkqy2ru2smW1+EckQNrM8miv5dGY0S11w+w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=chenbo.xia@outlook.com \
    --cc=dev@dpdk.org \
    --cc=fengli@smartx.com \
    --cc=maxime.coquelin@redhat.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).