From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F104E45BC0; Thu, 24 Oct 2024 11:44:16 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6C787433E1; Thu, 24 Oct 2024 11:44:16 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id AE5824003C for ; Thu, 24 Oct 2024 11:44:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1729763054; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=GsiwJG+ZKiH4C68eVyXdTU6Id6I051bKYJBGz5qKniI=; b=WqNX7g9F0YjvlHS4SHAoxr78QOdkElEcpxE13aTgP8T0OU2my0vzDy93JM7PpnnBNZ26PT jiu2X3mOlWYeWXxs5hv2LBAACUnhWSZVc07b9D3231+jPCLPUTq0/d11l7h+rmpSrgBbU6 wQ4swRphqqJ/cYH5eHbFTIjpl3D+1mk= Received: from mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-221-eUGOsU4UOvyzcQ1LYFExxw-1; Thu, 24 Oct 2024 05:44:11 -0400 X-MC-Unique: eUGOsU4UOvyzcQ1LYFExxw-1 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-02.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 6278E1955D91; Thu, 24 Oct 2024 09:44:10 +0000 (UTC) Received: from max-p1.redhat.com (unknown [10.39.208.26]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 57912300018D; Thu, 24 Oct 2024 09:44:08 +0000 (UTC) From: Maxime Coquelin To: dev@dpdk.org, david.marchand@redhat.com, chenbox@nvidia.com Cc: Maxime Coquelin Subject: [PATCH v3 0/6] VDUSE reconnection fixes and cleanup Date: Thu, 24 Oct 2024 11:44:00 +0200 Message-ID: <20241024094406.3826637-1-maxime.coquelin@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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(-) -- 2.46.2