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 17:09:00 -0700 [thread overview]
Message-ID: <3B79BD9C.4BA3546@sun.com> (raw)
In-Reply-To: <3B79B5F3.C816CBED@sun.com> <20010814.163804.66057702.davem@redhat.com> <3B79BA07.B57634FD@sun.com> <20010814.165320.77058794.davem@redhat.com>
"David S. Miller" wrote:
>
> From: Tim Hockin <thockin@sun.com>
> Date: Tue, 14 Aug 2001 16:53:43 -0700
>
> 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 am saying there is no problem.
>
> In both cases, for a properly written application we ignore the
> invalid fds. The behavior is identical both before and after
> your change, so there is no reason to make it.
But for an application that (imho) is poorly written but IS COMPLIANT, it
fails.
This program is compliant, if your ulimit -n is maxxed out at 1048576.
I'm not saying it is good design, but it is compliant. The patch hurts
nothing and makes poll() that little bit more friendly.
#include <stdio.h>
#include <sys/poll.h>
#include <errno.h>
#include <string.h>
int
main(void)
{
static struct pollfd ar[1024*1024];
int size = sizeof(ar)/sizeof(*ar);
int i;
for (i = 0; i < size; i++)
ar[i].fd = -1;
ar[1000000].fd = 0;
ar[1000000].events = POLLIN;
i = poll(ar, size, -1);
printf("return = %d (%s)\n", i, i?strerror(errno):"success");
return 0;
}
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com
next prev parent reply other threads:[~2001-08-15 0:05 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 ` RFC: poll change Tim Hockin
2001-08-14 23:53 ` David S. Miller
2001-08-15 0:08 ` Andrea Arcangeli
2001-08-15 0:09 ` Tim Hockin [this message]
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=3B79BD9C.4BA3546@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox