[PATCH 1/2] net/mlx5: improve socket file path
Bruce Richardson
bruce.richardson at intel.com
Fri Dec 13 18:16:23 CET 2024
On Fri, Dec 13, 2024 at 09:12:39AM -0800, Stephen Hemminger wrote:
> On Fri, 13 Dec 2024 17:24:42 +0800
> Yang Ming <ming.1.yang at nokia-sbell.com> wrote:
>
> > 1. /var/tmp is hard code which is not a good style
> > 2. /var/tmp may be not allowed to be written via container's
> > read only mode.
> >
> > Signed-off-by: Yang Ming <ming.1.yang at nokia-sbell.com>
>
> Since this is a unix domain socket, why not use abstract socket
> that doesn't have to be associated with filesystem?
In general, I think we should avoid abstract sockets in DPDK. Primary
reason is that they are linux-specific. Last time I checked other unixes,
like BSD, don't support them. A secondary concern is that having a
filesystem path allows permission checks, so for e.g. telemetry sockets,
only users with appropriate permissions can connect. With an abstract socket
we'd have to open up the area of user authentication.
/Bruce
More information about the dev
mailing list