[DPDK/ethdev Bug 1973] net/af_xdp: default dp_path uses /tmp

[DPDK/ethdev Bug 1973] net/af_xdp: default dp_path uses /tmp

[bugzilla]

http://bugs.dpdk.org/show_bug.cgi?id=1973

            Bug ID: 1973
           Summary: net/af_xdp: default dp_path uses /tmp
           Product: DPDK
           Version: 26.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

When use_cni=1 or use_pinned_map=1 is set without an explicit dp_path, the PMD
defaults the UDS / pinned-map path under /tmp/afxdp_dp/<if_name>/...
(DP_BASE_PATH in drivers/net/af_xdp/rte_eth_af_xdp.c).

Two related problems:

/tmp does not match current Linux file-hierarchy conventions for runtime
sockets. These belong under the runtime directory (/run, e.g.
rte_eal_get_runtime_dir()), not world-writable /tmp.

The AF_XDP Device Plugin for Kubernetes integration assumes /tmp: the plugin
creates and mounts the socket, and the PMD default hardcodes the same /tmp path
to match it. The location is effectively a contract duplicated in both
projects.
Note: the <if_name> component must be kept in any fix — it disambiguates
multiple UDS servers in one pod (added by the "fix multi interface support for
K8s" series).

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