mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thomas Meyer <thomas@m3y3r.de>, Al Viro <viro@zeniv.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Linux 3.3-rc4
Date: Wed, 22 Feb 2012 00:10:48 +0100	[thread overview]
Message-ID: <1329865848.18384.64.camel@edumazet-laptop> (raw)
In-Reply-To: <CA+55aFxkbsZN3yG6d9DPGiXmiuX-wOURJcC0hAUN3Qbykv1UhQ@mail.gmail.com>

Le mardi 21 février 2012 à 14:43 -0800, Linus Torvalds a écrit :
> On Sun, Feb 19, 2012 at 5:42 AM, Thomas Meyer <thomas@m3y3r.de> wrote:
> >
> > 2.) while debugging above issue: I did find an minor bug in sys_poll() - nobody did take care of my proposed patch: https://lkml.org/lkml/2011/9/24/35
> 
> Ok, so I started out forward-porting that patch to current -git
> (trivial: it's just that the system call tables are differently
> generated now), but the more I look at it, the more I suspect that we
> should perhaps just globally fix "sys_poll()" to have the timeout
> argument be 'int'.
> 
> Because that *is* the standard user interface (just do "man 2 poll"),
> and while all of the git history (and all of the BK history) we've had
> it as "long", I suspect we should just fix it.
> 
> So I suspect the correct patch is just as attached instead: make
> sys_poll() just take an "int timeout". Any user who tried to use a
> long value would already have got truncated by glibc - I just checked.
> 
> Of course, there is a remote possibility that somebody might not use
> glibc, and have used "poll()" with the raw system call interface, and
> depended on using a 64-bit "long timeout" on 64-bit architectures.
> 
> But quite frankly, that sounds rather unlikely in the extreme.
> 
> Comments? If we do this, and somebody actually reports that they use a
> 64-bit timeout, we could always go back to the broken 'long' argument,
> and take your patch to fix the compat case.
> 
>                   Linus

Yep, this is what I thought, but when this was raised last september,
both Andrew and Andi disagreed.

https://lkml.org/lkml/2011/10/6/389




  reply	other threads:[~2012-02-21 23:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19  0:27 Linus Torvalds
2012-02-19 13:42 ` Thomas Meyer
2012-02-19 18:45   ` Linus Torvalds
2012-02-19 19:49     ` David Miller
2012-02-19 20:02       ` Linus Torvalds
2012-02-20  3:28         ` Ian Kent
2012-02-21  3:29         ` Ian Kent
2012-02-21  3:38           ` Linus Torvalds
2012-02-21  4:02             ` Ian Kent
2012-02-21  4:17               ` Linus Torvalds
2012-02-21  4:52                 ` Ian Kent
2012-02-21  5:06                   ` Linus Torvalds
2012-02-21  5:21                     ` Linus Torvalds
2012-02-21  5:27                       ` H. Peter Anvin
2012-02-21  5:28                     ` H. Peter Anvin
2012-02-21  5:32                       ` Linus Torvalds
2012-02-21  5:39                     ` Ian Kent
2012-02-21  4:18           ` H. Peter Anvin
2012-02-21  4:22         ` H. Peter Anvin
2012-02-21 13:03           ` Alan Cox
2012-02-21 18:26             ` Use gcc to check exported files [Was: Linux 3.3-rc4] Sam Ravnborg
2012-02-21 18:58     ` Linux 3.3-rc4 Thomas Meyer
2012-02-21 22:07       ` Linus Torvalds
2012-02-21 22:43   ` Linus Torvalds
2012-02-21 23:10     ` Eric Dumazet [this message]
2012-02-21 23:19       ` Linus Torvalds
2012-02-24 10:39 ` Jiri Kosina
2012-02-24 16:52   ` Linus Torvalds
2012-02-24 18:01     ` Jiri Kosina
2012-02-24 18:21       ` Linus Torvalds
2012-02-29  8:38       ` Jiri Kosina

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=1329865848.18384.64.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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®