mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vadim Lobanov <vlobanov@speakeasy.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix poll() nfds check.
Date: Wed, 5 Jul 2006 21:02:15 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0607052050560.27726@shell3.speakeasy.net> (raw)
In-Reply-To: <20060705203959.53e128ef.akpm@osdl.org>

On Wed, 5 Jul 2006, Andrew Morton wrote:

> On Wed, 5 Jul 2006 20:00:34 -0700 (PDT)
> Vadim Lobanov <vlobanov@speakeasy.net> wrote:
>
> > diff -Npru linux-2.6.17-git25/fs/select.c linux-new/fs/select.c
> > --- linux-2.6.17-git25/fs/select.c	2006-07-05 19:06:56.000000000 -0700
> > +++ linux-new/fs/select.c	2006-07-05 19:10:51.000000000 -0700
> > @@ -671,7 +671,7 @@ int do_sys_poll(struct pollfd __user *uf
> >  	fdt = files_fdtable(current->files);
> >  	max_fdset = fdt->max_fdset;
> >  	rcu_read_unlock();
> > -	if (nfds > max_fdset && nfds > OPEN_MAX)
> > +	if (nfds > max_fdset)
> >  		return -EINVAL;
> >
> >  	poll_initwait(&table);
>
> http://www.opengroup.org/onlinepubs/009695399/functions/poll.html sayeth
>
> [EINVAL]
>     The nfds argument is greater than {OPEN_MAX}, or ...
>
> and afaict, max_fdset can be either less than or greater than OPEN_MAX,
> depending upon how one sets NR_OPEN.

Very good point. My manpages have led me astray to the dark side. :)

> So I think that patch should be s/&&/||/ and s/changelog/new one/

Yikes, I think sticking the OR operator in there would seriously suck,
given that programs would then be unable to poll on more than 256 file
descriptors (which actually happens, or so I've heard). Besides, it
would also kill Tigran's work, as per the comment from the top of
select.c:

012  *  24 January 2000
013  *     Changed sys_poll()/do_poll() to use PAGE_SIZE chunk-based allocation
014  *     of fds to overcome nfds < 16390 descriptors limit (Tigran Aivazian).
015  */

> If anything we do here alters userspace-visible behaviour (and it probably will)
> then it should be *exahustively* documented in the changelog, and probably dropped.

Arguments of the cited standard's sensibilities notwithstanding (given
that it seems silly to limit the API in unnatural ways, as we can easily
and provably handle more than 256 fds), it seems better to leave this as
is. Thanks for the critical eye. :)

- Vadim Lobanov

  reply	other threads:[~2006-07-06  4:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  3:00 Vadim Lobanov
2006-07-06  3:39 ` Andrew Morton
2006-07-06  4:02   ` Vadim Lobanov [this message]
2006-07-06 15:44   ` Ulrich Drepper
2006-07-06 16:28     ` Vadim Lobanov
2006-07-07  3:00 ` H. Peter Anvin

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=Pine.LNX.4.58.0607052050560.27726@shell3.speakeasy.net \
    --to=vlobanov@speakeasy.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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®