From: Joseph Myers <joseph@codesourcery.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Ping Re: Fix bits/socket.h IOC* namespace issues (bug 21267)
Date: Mon, 27 Mar 2017 14:46:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1703271442500.22801@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAK8P3a2i9megdoUEnreiXiyt1DJ8P+meprN=vi2Z3nYtO3HwmQ@mail.gmail.com>
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
<asm/ioctl.h> (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
next prev parent reply other threads:[~2017-03-27 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 0:31 Joseph Myers
2017-03-23 17:59 ` Ping " Joseph Myers
2017-03-24 14:06 ` Arnd Bergmann
2017-03-27 14:46 ` Joseph Myers [this message]
2017-04-05 16:14 ` Ping^2 " Joseph Myers
2017-04-06 19:01 ` Adhemerval Zanella
2017-04-18 21:29 ` Joseph Myers
2017-04-20 19:11 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1703271442500.22801@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=arnd@arndb.de \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).