All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 215] IPC socket of 2 primary processes may conflict
Date: Tue, 26 Feb 2019 16:14:23 +0000	[thread overview]
Message-ID: <bug-215-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 215
           Summary: IPC socket of 2 primary processes may conflict
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: thomas@monjalon.net
                CC: anatoly.burakov@intel.com
  Target Milestone: ---

After some code reading, it seems we do not use hugefile_prefix in the path
name of the IPC socket.
So the channel to communicate with its secondary processes will be the same for
two different primary processes.

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

             reply	other threads:[~2019-02-26 16:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 16:14 bugzilla [this message]
2019-02-26 16:19 ` [Bug 215] IPC socket of 2 primary processes may conflict bugzilla

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-215-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.