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 074B1438AC;
Sat, 13 Jan 2024 06:59:39 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
by mails.dpdk.org (Postfix) with ESMTP id 8DACC40268;
Sat, 13 Jan 2024 06:59:38 +0100 (CET)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
by mails.dpdk.org (Postfix) with ESMTP id D371B400EF
for ; Sat, 13 Jan 2024 06:59:36 +0100 (CET)
Received: by inbox.dpdk.org (Postfix, from userid 33)
id B988F438AE; Sat, 13 Jan 2024 06:59:36 +0100 (CET)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1364] telemetry conns may leak in certain situation
Date: Sat, 13 Jan 2024 05:59:35 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: other
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 1819846787@qq.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dev@dpdk.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
op_sys bug_status bug_severity priority component assigned_to reporter
target_milestone
Message-ID:
Content-Type: multipart/alternative; boundary=17051255760.c3D7c.3834114
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
MIME-Version: 1.0
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
--17051255760.c3D7c.3834114
Date: Sat, 13 Jan 2024 06:59:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
https://bugs.dpdk.org/show_bug.cgi?id=3D1364
Bug ID: 1364
Summary: telemetry conns may leak in certain situation
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: 1819846787@qq.com
Target Milestone: ---
Every time the telemetry server successfully returns from the accept, it
atomically increases the value of num_clients=EF=BC=88if < MAX_CONNECTIONS=
=EF=BC=89 and then
executes pthread_create to create a thread to execute the client_handler
function. In this function, some information will be written to the client.=
If
the write fails, the thread returns NULL without atomically reducing
num_clients, this will cause the Telemetry server to run for a period of ti=
me,
and the value of num_clients will be greater than 10, resulting in telemetry
being unavailable.=20
Therefore, the decrease in atomicity v2_clients should occur after the writ=
e()
failure
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--17051255760.c3D7c.3834114
Date: Sat, 13 Jan 2024 06:59:36 +0100
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.dpdk.org/
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
Every time the telemetry server su=
ccessfully returns from the accept, it
atomically increases the value of num_clients=EF=BC=88if < MAX_CONNECTIO=
NS=EF=BC=89 and then
executes pthread_create to create a thread to execute the client_handler
function. In this function, some information will be written to the client.=
If
the write fails, the thread returns NULL without atomically reducing
num_clients, this will cause the Telemetry server to run for a period of ti=
me,
and the value of num_clients will be greater than 10, resulting in telemetry
being unavailable.=20
Therefore, the decrease in atomicity v2_clients should occur after the writ=
e()
failure