All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@sun.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RFC: poll change
Date: Tue, 14 Aug 2001 16:53:43 -0700	[thread overview]
Message-ID: <3B79BA07.B57634FD@sun.com> (raw)
In-Reply-To: <3B79B381.58266C13@sun.com> <20010814.162710.131914269.davem@redhat.com> <3B79B5F3.C816CBED@sun.com> <20010814.163804.66057702.davem@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

"David S. Miller" wrote:
 
>    The standard also says that any pollfd with (fd < 0) is ignored.  Holes are
>    explicitly ALLOWED.
> 
> Dude, it ignores negative fds, check fs/select.c:do_pollfd()

Right - we're running in circles.

The standard says negative fd's are ignored.  We get that right.  What we
are left with is an overly paranoid check against max_fds.  This check
should go away.  You should be able to pass in up to your rlimit fds, and
let negative ones (holes or tails) be ignored.

I'm attaching a patch :).

Am I still not making the problem clear?

-- 
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com

[-- Attachment #2: select.diff --]
[-- Type: text/plain, Size: 583 bytes --]

Index: fs/select.c
===================================================================
RCS file: /home/cvs/linux-2.4/fs/select.c,v
retrieving revision 1.5
diff -u -r1.5 select.c
--- fs/select.c	2001/07/09 23:10:25	1.5
+++ fs/select.c	2001/08/14 23:47:46
@@ -416,11 +416,8 @@
 	int nchunks, nleft;
 
 	/* Do a sanity check on nfds ... */
-	if (nfds > NR_OPEN)
+	if (nfds > current->rlim[RLIMIT_NOFILE].rlim_cur)
 		return -EINVAL;
-
-	if (nfds > current->files->max_fds)
-		nfds = current->files->max_fds;
 
 	if (timeout) {
 		/* Careful about overflow in the intermediate values */

       reply	other threads:[~2001-08-14 23:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B79B381.58266C13@sun.com>
     [not found] ` <20010814.162710.131914269.davem@redhat.com>
     [not found]   ` <3B79B5F3.C816CBED@sun.com>
     [not found]     ` <20010814.163804.66057702.davem@redhat.com>
2001-08-14 23:53       ` Tim Hockin [this message]
2001-08-14 23:53         ` RFC: poll change David S. Miller
2001-08-15  0:08           ` Andrea Arcangeli
2001-08-15  0:09           ` Tim Hockin
2001-08-15  0:06             ` David S. Miller
2001-08-15  0:11         ` Andrea Arcangeli
2001-08-15  0:16           ` David S. Miller
2001-08-15  0:30             ` Andrea Arcangeli
2001-08-15  0:34             ` [PATCH] agreed upon " Tim Hockin
2001-08-15  0:32               ` David S. Miller
2001-08-15 14:13             ` RFC: " Andrea Arcangeli
2001-08-15 14:24               ` David S. Miller
2001-08-15 14:32                 ` Andrea Arcangeli
2001-08-15 16:30                   ` Hugh Dickins
2001-08-15 16:40                     ` Andrea Arcangeli
2001-08-14 21:08 Tim Hockin
2001-08-14 21:43 ` David S. Miller
2001-08-14 22:38   ` Herbert Xu
2001-08-14 22:42     ` David S. Miller
2001-08-15  0:03       ` Andrea Arcangeli
2001-08-15  0:06         ` David S. Miller
2001-08-15  0:16           ` Andrea Arcangeli
2001-08-15  0:23             ` David S. Miller
2001-08-15 10:40       ` David Schwartz

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=3B79BA07.B57634FD@sun.com \
    --to=thockin@sun.com \
    --cc=davem@redhat.com \
    --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 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.