summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorVernon Mauery <vernon.mauery@linux.intel.com>2018-12-19 10:33:46 -0800
committerVernon Mauery <vernon.mauery@linux.intel.com>2018-12-19 18:45:12 +0000
commitdbc46919bddedb159d05558053963df40b2c9300 (patch)
treeb1560c28dacec0c4d4e064d3c3a8ce1992e80538 /MAINTAINERS
parent0f7019df1ecf905c72378dc9a3dcab625bb142b7 (diff)
downloadphosphor-rest-server-dbc46919bddedb159d05558053963df40b2c9300.tar.gz
phosphor-rest-server-dbc46919bddedb159d05558053963df40b2c9300.zip
phosphor-rest-server: connect with the correct sockaddr size
With the obmc-console-server binding to the correct socket, this is not needed. Abstract unix sockets start with the nul-charater, but are not nul terminated. In fact, the nul-character has no meaning in the path. According to the man page unix(7), abstract: an abstract socket address is distinguished (from a pathname socket) by the fact that sun_path[0] is a null byte ('\0'). The socket's address in this namespace is given by the additional bytes in sun_path that are covered by the specified length of the address structure. (Null bytes in the name have no special significance.) This means that when calling bind/connect, the size of the sockaddr structure is not sizeof(sockaddr_un), it is sizeof(sockaddr_un) - sizeof(sun_path) + (path_len) Change-Id: I1d978af9ace7fa137bab2f596a217d1ba243e5be Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud