mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	law@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] posix_types.h: make __NFDBITS compatible with glibc definition
Date: Tue, 24 Jul 2012 15:03:03 -0400	[thread overview]
Message-ID: <20120724190302.GE10534@zod.bos.redhat.com> (raw)
In-Reply-To: <CA+55aFwFcWoH=QB5tKgVjWcUH3SLCDVNqJY-oXRYy7AWOJfLPA@mail.gmail.com>

On Tue, Jul 24, 2012 at 11:46:25AM -0700, Linus Torvalds wrote:
> On Tue, Jul 24, 2012 at 11:32 AM, Josh Boyer <jwboyer@redhat.com> wrote:
> > Recent glibc made a change to suppress sign-conversion warnings from FD_SET
> > (glibc commit ceb9e56b3d1).  That patch solved the particular error it was
> > aiming to, however applications that #include <linux/types.h> after
> > including <sys/select.h> can now hit a build failure if -Werror=sign-compare
> > and -D_FORTIFY_SOURCE=2 is passed to gcc.  This can be seen when building
> > this trivial application against a recent enough glibc:
> 
> Looking more at this, I now hate it for *another* reason.
> 
> Making __NFDBITS be a signed value turns __FDELT() and __FDMASK() into
> potentially pure and utter crap. Doing signed divisions (or modulus)
> is a disaster - suddenly it's not just a bit shift any more.
> 
> Guys, the glibc people really seem to not have thought their change
> through. Or maybe they fixed their __FDELT/__FDMASK at the same time?

Jeff can probably answer this better than I can, so likely best to wait
for him.

FWIW, the definitions of __FD_ELT/__FD_MASK in glibc are:

#define __FD_ELT(d)     ((d) / __NFDBITS)
#define __FD_MASK(d)    ((__fd_mask) 1 << ((d) % __NFDBITS))

where __fd_mask is 'typdef long int'.

__NFDBITS was changed to int type with glibc commit eb0b6cb6e in 2009,
and __FDELT/__FDMASK were basically renamed with glibc commit
e529793b508 in 2011.

josh

  reply	other threads:[~2012-07-24 19:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 18:12 [PATCH] posix_types.h: make __NFDBITS match " Josh Boyer
2012-07-24 18:20 ` Linus Torvalds
2012-07-24 18:24   ` Josh Boyer
2012-07-24 18:32     ` [PATCH v2] posix_types.h: make __NFDBITS compatible with " Josh Boyer
2012-07-24 18:46       ` Linus Torvalds
2012-07-24 19:03         ` Josh Boyer [this message]
2012-07-24 19:09           ` Linus Torvalds
2012-07-24 19:15             ` Jeff Law
2012-07-24 19:24               ` Linus Torvalds
2012-07-24 19:26                 ` Jeff Law
2012-07-24 19:43                   ` Josh Boyer
2012-07-24 19:55                     ` Linus Torvalds
2012-07-24 20:10                       ` Josh Boyer
2012-07-24 20:13                         ` Linus Torvalds
2012-07-24 20:02                     ` Andreas Schwab
2012-07-24 19:43                   ` Linus Torvalds
2012-07-24 20:01                     ` Jeff Law
2012-07-24 19:19     ` [PATCH] posix_types.h: make __NFDBITS match " Jeff Law
2012-07-24 19:37       ` Linus Torvalds
2012-07-24 19:39         ` Linus Torvalds
2012-07-24 19:41         ` Josh Boyer
2012-07-24 19:59           ` Linus Torvalds
2012-07-24 20:11             ` Linus Torvalds
2012-07-24 20:52               ` Andreas Schwab

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=20120724190302.GE10534@zod.bos.redhat.com \
    --to=jwboyer@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=law@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®