All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 662] Pthread_mutex usage is not safe between primar/secondary process
Date: Mon, 15 Mar 2021 19:22:28 +0000	[thread overview]
Message-ID: <bug-662-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 662
           Summary: Pthread_mutex usage is not safe between
                    primar/secondary process
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

Posix mutex's are by default private to the process creating them. Several
places in DPDK use pthread_mutex to protect resources in a manner that is not
safe when used with primary/secondary processes.

This problem was reported against failsafe driver, but it seems to be a wider
problem (assumptions in DPDK). Initial report was on 18.11, but these bugs go
back to original code in many cases.

Mutexes that are protecting data structures from multi-process model must call
pthread_setpshared().

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

                 reply	other threads:[~2021-03-15 19:22 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-662-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.