All of lore.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-1364-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1364

            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(if < MAX_CONNECTIONS) 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 time,
and the value of num_clients will be greater than 10, resulting in telemetry
being unavailable. 
Therefore, the decrease in atomicity v2_clients should occur after the write()
failure

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3066 bytes --]

                 reply	other threads:[~2024-01-13  5:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1364-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.