From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21]) by sourceware.org (Postfix) with ESMTPS id 1AAFD385702E for ; Mon, 29 Mar 2021 08:22:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 1AAFD385702E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=deneb.enyo.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=fw@deneb.enyo.de Received: from [172.17.203.2] (port=42075 helo=deneb.enyo.de) by albireo.enyo.de ([172.17.140.2]) with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1lQnAM-0002E1-HZ; Mon, 29 Mar 2021 08:22:30 +0000 Received: from fw by deneb.enyo.de with local (Exim 4.92) (envelope-from ) id 1lQnAM-0001Ko-Cb; Mon, 29 Mar 2021 10:22:30 +0200 From: Florian Weimer To: Daniel Black Cc: libc-alpha@sourceware.org Subject: Re: [PATCH] inet: getnameinfo fix serv for abstract socket [BZ #27634] References: <20210327052649.1728350-1-daniel@mariadb.org> <87tuow77c0.fsf@mid.deneb.enyo.de> Date: Mon, 29 Mar 2021 10:22:30 +0200 In-Reply-To: (Daniel Black's message of "Sun, 28 Mar 2021 09:32:43 +1100") Message-ID: <87h7kuwerd.fsf@mid.deneb.enyo.de> MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 08:22:33 -0000 * Daniel Black: >> How the path is mapped between the host and >> service names also differs. > > With the portability differences, in the case that a service name > happens to start with \0 (is there one?) there are two possible > cases: > > * sbuf gets populated with exactly what was in sun_path, I thought this was > pretty portable. > * if NI_MAXSERV wasn't used, you may end up with EAI_OVERFLOW What I meant is that some implementations put the socket name into the host name, not the service name. The length restrictions you discovered might be related to that.