From: Florian Weimer <fw@deneb.enyo.de> To: Arnd Bergmann <arnd@arndb.de> Cc: "David S . Miller" <davem@davemloft.net>, Deepa Dinamani <deepa.kernel@gmail.com>, Willem de Bruijn <willemb@google.com>, alpha <linux-alpha@vger.kernel.org>, linux-arch <linux-arch@vger.kernel.org>, linux-mips@vger.kernel.org, Parisc List <linux-parisc@vger.kernel.org>, sparclinux <sparclinux@vger.kernel.org>, Laura Abbott <labbott@redhat.com>, Networking <netdev@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux API <linux-api@vger.kernel.org> Subject: Re: [PATCH] y2038: fix socket.h header inclusion Date: Fri, 15 Mar 2019 22:20:04 +0100 [thread overview] Message-ID: <87a7hvded7.fsf@mid.deneb.enyo.de> (raw) In-Reply-To: <CAK8P3a1r8GRC7GTHHqWY-PUn=9rWB-7+Qo=7txanbEjGZ-wppw@mail.gmail.com> (Arnd Bergmann's message of "Fri, 15 Mar 2019 21:30:25 +0100") * Arnd Bergmann: > On Thu, Mar 14, 2019 at 7:41 PM Florian Weimer <fw@deneb.enyo.de> wrote: >> >> * Arnd Bergmann: >> >> > diff --git a/arch/alpha/include/uapi/asm/socket.h >> > b/arch/alpha/include/uapi/asm/socket.h >> > index 0d0fddb7e738..976e89b116e5 100644 >> > --- a/arch/alpha/include/uapi/asm/socket.h >> > +++ b/arch/alpha/include/uapi/asm/socket.h >> > @@ -2,8 +2,8 @@ >> > #ifndef _UAPI_ASM_SOCKET_H >> > #define _UAPI_ASM_SOCKET_H >> > >> > +#include <linux/posix_types.h> >> > #include <asm/sockios.h> >> > -#include <asm/bitsperlong.h> >> >> This breaks POSIX conformance in glibc because the >> <linux/posix_types.h> header is not namespace clean. It contains the >> identifiers fds_bits and val: >> >> unsigned long fds_bits[__FD_SETSIZE / (8 * sizeof(long))]; >> >> int val[2]; > > What is problematic about the struct members here? I had thought that > only the struct names have to be in a namespace to be usable here, > but not the members. According POSIX, a user can do this: #define fds_bits 1024 before including the <sys/socket.h> header file. Similarly for val. Since glibc pulls in <asm/socket.h> indirectly, the result is a parse error, even though the programmer did nothing wrong (fds_bits is not an identifier used by POSIX, nor is it in the implementation namespace, ans <sys/socket.h> is a POSIX header). > We could use asm/posix_types.h instead of linux/posix_types.h, > would that address your concern? It should fix the fds_bits case, I think. But <asm-generic/posix_types.h> still uses val, so that part of the issue remains.
WARNING: multiple messages have this Message-ID (diff)
From: Florian Weimer <fw@deneb.enyo.de> To: Arnd Bergmann <arnd@arndb.de> Cc: "David S . Miller" <davem@davemloft.net>, Deepa Dinamani <deepa.kernel@gmail.com>, Willem de Bruijn <willemb@google.com>, alpha <linux-alpha@vger.kernel.org>, linux-arch <linux-arch@vger.kernel.org>, linux-mips@vger.kernel.org, Parisc List <linux-parisc@vger.kernel.org>, sparclinux <sparclinux@vger.kernel.org>, Laura Abbott <labbott@redhat.com>, Networking <netdev@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Linux API <linux-api@vger.kernel.org> Subject: Re: [PATCH] y2038: fix socket.h header inclusion Date: Fri, 15 Mar 2019 21:20:04 +0000 [thread overview] Message-ID: <87a7hvded7.fsf@mid.deneb.enyo.de> (raw) In-Reply-To: <CAK8P3a1r8GRC7GTHHqWY-PUn=9rWB-7+Qo=7txanbEjGZ-wppw@mail.gmail.com> (Arnd Bergmann's message of "Fri, 15 Mar 2019 21:30:25 +0100") * Arnd Bergmann: > On Thu, Mar 14, 2019 at 7:41 PM Florian Weimer <fw@deneb.enyo.de> wrote: >> >> * Arnd Bergmann: >> >> > diff --git a/arch/alpha/include/uapi/asm/socket.h >> > b/arch/alpha/include/uapi/asm/socket.h >> > index 0d0fddb7e738..976e89b116e5 100644 >> > --- a/arch/alpha/include/uapi/asm/socket.h >> > +++ b/arch/alpha/include/uapi/asm/socket.h >> > @@ -2,8 +2,8 @@ >> > #ifndef _UAPI_ASM_SOCKET_H >> > #define _UAPI_ASM_SOCKET_H >> > >> > +#include <linux/posix_types.h> >> > #include <asm/sockios.h> >> > -#include <asm/bitsperlong.h> >> >> This breaks POSIX conformance in glibc because the >> <linux/posix_types.h> header is not namespace clean. It contains the >> identifiers fds_bits and val: >> >> unsigned long fds_bits[__FD_SETSIZE / (8 * sizeof(long))]; >> >> int val[2]; > > What is problematic about the struct members here? I had thought that > only the struct names have to be in a namespace to be usable here, > but not the members. According POSIX, a user can do this: #define fds_bits 1024 before including the <sys/socket.h> header file. Similarly for val. Since glibc pulls in <asm/socket.h> indirectly, the result is a parse error, even though the programmer did nothing wrong (fds_bits is not an identifier used by POSIX, nor is it in the implementation namespace, ans <sys/socket.h> is a POSIX header). > We could use asm/posix_types.h instead of linux/posix_types.h, > would that address your concern? It should fix the fds_bits case, I think. But <asm-generic/posix_types.h> still uses val, so that part of the issue remains.
next prev parent reply other threads:[~2019-03-15 21:20 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-11 15:38 [PATCH] y2038: fix socket.h header inclusion Arnd Bergmann 2019-03-11 15:38 ` Arnd Bergmann 2019-03-11 18:23 ` David Miller 2019-03-11 18:23 ` David Miller 2019-03-14 18:37 ` Florian Weimer 2019-03-14 18:37 ` Florian Weimer 2019-03-15 20:30 ` Arnd Bergmann 2019-03-15 20:30 ` Arnd Bergmann 2019-03-15 21:20 ` Florian Weimer [this message] 2019-03-15 21:20 ` Florian Weimer 2019-03-17 18:20 ` Deepa Dinamani 2019-03-17 18:20 ` Deepa Dinamani 2019-03-18 8:27 ` Arnd Bergmann 2019-03-18 8:27 ` Arnd Bergmann 2019-03-18 9:21 ` Florian Weimer 2019-03-18 9:21 ` Florian Weimer 2019-03-18 12:56 ` Arnd Bergmann 2019-03-18 12:56 ` Arnd Bergmann 2019-03-18 13:12 ` Florian Weimer 2019-03-18 13:12 ` Florian Weimer 2019-03-18 13:12 ` Florian Weimer 2019-03-18 14:34 ` Arnd Bergmann 2019-03-18 14:34 ` Arnd Bergmann 2019-03-18 14:34 ` Arnd Bergmann 2019-03-18 14:37 ` Florian Weimer 2019-03-18 14:37 ` Florian Weimer
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=87a7hvded7.fsf@mid.deneb.enyo.de \ --to=fw@deneb.enyo.de \ --cc=arnd@arndb.de \ --cc=davem@davemloft.net \ --cc=deepa.kernel@gmail.com \ --cc=labbott@redhat.com \ --cc=linux-alpha@vger.kernel.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux-parisc@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=sparclinux@vger.kernel.org \ --cc=willemb@google.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.