IPC socket of 2 primary processes may conflict

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: [email protected]
Reporter: [email protected]
CC: [email protected]
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.

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

Anatoly Burakov ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Anatoly Burakov ([email protected]) --- This is incorrect. Socket path is generated from create_socket_path() call at eal_common_proc.c:135. That, in turn, will call eal_mp_socket_path(), which uses rte_eal_get_runtime_dir() to get its path. That path includes the hugefile prefix.

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