From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1973] net/af_xdp: default dp_path uses /tmp
Date: Thu, 23 Jul 2026 16:56:45 +0000 [thread overview]
Message-ID: <bug-1973-3@http.bugs.dpdk.org/> (raw)
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.
reply other threads:[~2026-07-23 16:56 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-1973-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.