From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99998 invoked by alias); 27 Mar 2017 14:46:44 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 99971 invoked by uid 89); 27 Mar 2017 14:46:42 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=IOR X-HELO: relay1.mentorg.com Date: Mon, 27 Mar 2017 14:46:00 -0000 From: Joseph Myers To: Arnd Bergmann CC: GNU C Library Subject: Re: Ping Re: Fix bits/socket.h IOC* namespace issues (bug 21267) In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) X-SW-Source: 2017-03/txt/msg00621.txt.bz2 On Fri, 24 Mar 2017, Arnd Bergmann wrote: > There are many exported or user-space provided headers that include > linux/ioctl.h or asm/ioctl.h in order to get the _IOC/IOW/IOR/IOWR > macros: That's what I expect them to be used for. > so any of them will also pull in IOC_IN/INOUT/OUT. Is mips/asm/sockios.h > the only one in that list that i problematic for glibc, or should they > all avoid the macros if possible? Only mips/asm/sockios.h is currently observed to cause namespace problems. alpha's asm/sockios.h also uses _IOR/_IOW macros, but without including (so I suppose the macros defined using _IOR/_IOW might not actually work unless a source of those macro definitions gets included explicitly). -- Joseph S. Myers joseph@codesourcery.com