DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com
Subject: Re: [PATCH v3 0/6] VDUSE reconnection fixes and cleanup
Date: Thu, 24 Oct 2024 13:42:26 +0200	[thread overview]
Message-ID: <11e8ae6b-e546-4c33-a04b-547ed2d4d213@redhat.com> (raw)
In-Reply-To: <20241024094406.3826637-1-maxime.coquelin@redhat.com>



On 10/24/24 11:44, Maxime Coquelin wrote:
> This series provides various fixes for VDUSE reconnection
> introduced in -rc1, some of them being reported by
> Coverity.
> 
> The series also takes the opportunity to refactor
> reconnection to make it more self-contained to simplify
> readability and error path handling.
> 
> Changes in v2:
> ==============
> - Avoid superluous error logging (David)
> - VDUSE in capital letter in commit title 1 (David)
> - Declare dev_config in the code block it is used (David)
> - Fix wrong goto in intermediate patch (Maxime)
> 
> Maxime Coquelin (6):
>    vhost: fix VDUSE device creation error handling
>    vhost: fix possible TOCTOU in VDUSE dev creation
>    vhost: fix VDUSE reconnect device start failure
>    vhost: refactor VDUSE reconnection log mapping
>    vhost: fix and refactor VDUSE reconnect log check
>    vhost: move VDUSE reconnection after device is created
> 
>   lib/vhost/vduse.c | 322 ++++++++++++++++++++++++++--------------------
>   1 file changed, 181 insertions(+), 141 deletions(-)
> 

Applied to next-virtio/for-next-net

Thanks,
Maxime


      parent reply	other threads:[~2024-10-24 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24  9:44 Maxime Coquelin
2024-10-24  9:44 ` [PATCH v3 1/6] vhost: fix VDUSE device creation error handling Maxime Coquelin
2024-10-24 10:03   ` David Marchand
2024-10-24  9:44 ` [PATCH v3 2/6] vhost: fix possible TOCTOU in VDUSE dev creation Maxime Coquelin
2024-10-24  9:44 ` [PATCH v3 3/6] vhost: fix VDUSE reconnect device start failure Maxime Coquelin
2024-10-24 10:04   ` David Marchand
2024-10-24  9:44 ` [PATCH v3 4/6] vhost: refactor VDUSE reconnection log mapping Maxime Coquelin
2024-10-24 10:04   ` David Marchand
2024-10-24  9:44 ` [PATCH v3 5/6] vhost: fix and refactor VDUSE reconnect log check Maxime Coquelin
2024-10-24 10:04   ` David Marchand
2024-10-24  9:44 ` [PATCH v3 6/6] vhost: move VDUSE reconnection after device is created Maxime Coquelin
2024-10-24 10:04   ` David Marchand
2024-10-24 11:42 ` Maxime Coquelin [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=11e8ae6b-e546-4c33-a04b-547ed2d4d213@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbox@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@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).