From: Jamie Lokier <jamie@shareable.org>
To: Tim Hockin <thockin@sun.com>
Cc: Jim Houston <jim.houston@ccur.com>, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, viro@parcelfarce.linux.theplanet.co.uk,
linux-kernel@vger.kernel.org, george@mvista.com
Subject: Re: PATCH - raise max_anon limit
Date: Fri, 13 Feb 2004 02:01:13 +0000 [thread overview]
Message-ID: <20040213020113.GD25499@mail.shareable.org> (raw)
In-Reply-To: <20040212184903.GS9155@sun.com>
Tim Hockin wrote:
> > The rational for avoiding immediate reuse of id values is to catch
> > application errors. Consider:
> >
> > fd1 = open_like_call(...);
> > read(fd1,...);
> > close(fd1);
> > fd2 = open_like_call(...);
> > write(fd1...);
> >
> > If fd2 has a different value than the recently closed fd1, the
> > error is detected immediately.
>
> Is that really worth working around in such a gross way? No offense to the
> idea, but that's a pretty dumb bug to be hacking a failsafe for :)
I'm pretty sure POSIX requires fd2 to be equal to fd1 if it is the
lowest free file descriptor number.
Unfortunately. An O(1) fd allocation algorithm would be nice.
-- Jamie
next prev parent reply other threads:[~2004-02-13 2:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 22:15 PATCH - raise max_anon limit Tim Hockin
2004-02-07 8:55 ` Andrew Morton
2004-02-07 9:48 ` viro
2004-02-11 20:33 ` Tim Hockin
2004-02-11 20:38 ` Linus Torvalds
2004-02-11 21:09 ` Tim Hockin
2004-02-11 21:53 ` Andrew Morton
2004-02-11 22:28 ` Tim Hockin
2004-02-11 22:48 ` Andrew Morton
[not found] ` <20040211233852.GN9155@sun.com>
[not found] ` <20040211155754.5068332c.akpm@osdl.org>
[not found] ` <20040212003840.GO9155@sun.com>
[not found] ` <20040211164233.5f233595.akpm@osdl.org>
2004-02-12 1:08 ` Tim Hockin
2004-02-12 1:20 ` Andrew Morton
2004-02-12 2:22 ` Tim Hockin
2004-02-12 17:26 ` Jim Houston
2004-02-12 18:49 ` Tim Hockin
2004-02-13 2:01 ` Jamie Lokier [this message]
2004-02-12 22:03 ` Andrew Morton
2004-02-13 1:12 ` George Anzinger
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=20040213020113.GD25499@mail.shareable.org \
--to=jamie@shareable.org \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=jim.houston@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.com \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.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