From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12637 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: Adding vsock related structures and #defines Date: Mon, 26 Mar 2018 19:47:48 +0200 Message-ID: <20180326174747.GA4418@port70.net> References: Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1522086749 2083 195.159.176.226 (26 Mar 2018 17:52:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Mar 2018 17:52:29 +0000 (UTC) User-Agent: Mutt/1.9.1 (2017-09-22) To: musl@lists.openwall.com Original-X-From: musl-return-12651-gllmg-musl=m.gmane.org@lists.openwall.com Mon Mar 26 19:52:25 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1f0WID-0000SH-4K for gllmg-musl@m.gmane.org; Mon, 26 Mar 2018 19:52:25 +0200 Original-Received: (qmail 32417 invoked by uid 550); 26 Mar 2018 17:48:05 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 32288 invoked from network); 26 Mar 2018 17:48:00 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline In-Reply-To: Xref: news.gmane.org gmane.linux.lib.musl.general:12637 Archived-At: * Ben Hillis [2018-03-26 16:35:15 +0000]: > I'm wondering if it would be possible to add the definitions for vsock sockets to the header files that are included in musl libc: > http://man7.org/linux/man-pages/man7/vsock.7.html These definitions are located in include/uapi/linux/vm_sockets.h. > AF_VSOCK support was added in http://git.musl-libc.org/cgit/musl/commit/?id=3d4583c3fba8989a596506619277ecd68768d9ab otoh the sockaddr type and VMADDR_* macros were not added, it's not obvious how to do that correctly: the type name is non-standard so it can only be exposed under _GNU_SOURCE and the man page says they live in linux/vm_sockets.h so putting it elsewhere will create conflicts if both linux and libc headers are included...