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 2D8ABA0524; Thu, 6 May 2021 11:45:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AB75B410DB; Thu, 6 May 2021 11:45:17 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 6244E40040 for ; Thu, 6 May 2021 11:45:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620294315; 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=SxgeK9hZSPyZysDdobJ7RVVkpZCiK8ddX2y9NxQIAFI=; b=V/tvFK0mvKlgCFytsin7NPGIU2qQoAtM9mAsFX9CWp7iDZY51WEM6WG3tP7VEra6WQmLEG wpKND8iifAQjSfd7VLVWFncghFb0vJlHJgT/7yEdhaX+PYod3ByF8bDW4uYFCUwvMMbCu5 bAyZs3eulv8FU2U0ZJhq2khTFDFv6fo= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-63-JB9Tskc_PxiRYzLW5I6NiQ-1; Thu, 06 May 2021 05:45:10 -0400 X-MC-Unique: JB9Tskc_PxiRYzLW5I6NiQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8DBB6800685; Thu, 6 May 2021 09:45:08 +0000 (UTC) Received: from dmarchan.remote.csb (unknown [10.40.192.60]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5EC035B4B5; Thu, 6 May 2021 09:45:00 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: timothy.mcdaniel@intel.com, maxime.coquelin@redhat.com, chenbo.xia@intel.com Date: Thu, 6 May 2021 11:44:50 +0200 Message-Id: <20210506094452.1689-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=david.marchand@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII" Subject: [dpdk-dev] [PATCH 0/2] Thread termination leak fixes 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 Sender: "dev" After looking at the control thread API use in recent changes, I noticed that some thread resources are not properly released. This series fixes two net drivers. Additional notes: - I noticed that event/dlb2 never kills/terminates its service thread. It means unplug of this device (if supported) would leak the associated thread resources. I leave it to this driver maintainer to comment/fix. - The vhost library also lets a service thread in the background but since there is no way to unitialize this library, there is no leak to fix from my pov. -- David Marchand David Marchand (2): net/ark: fix leak on thread termination net/ice: fix leak on thread termination drivers/net/ark/ark_pktgen.c | 2 ++ drivers/net/ice/ice_dcf_parent.c | 2 ++ 2 files changed, 4 insertions(+) -- 2.23.0