From: dank@kegel.com
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 'select' failure or signal should not update timeout
Date: Fri, 19 Jul 2002 20:59:30 -0700 [thread overview]
Message-ID: <3D38E022.4005981E@kegel.com> (raw)
Alan Cox wrote:
> > <http://www.opengroup.org/onlinepubs/007904975/functions/select.html>
> > says that 'select' may modify its timeout argument only "upon
> > successful completion". However, the Linux kernel sometimes modifies
> > the timeout argument even when 'select' fails or is interrupted.
>
> This is extremely useful behaviour. POSIX is broken here.
I tried to make use of this behavior back in 2.2 days, I think,
and ran into trouble. The time remaining wasn't quite right, I seem
to recall, making this nifty feature less useful. I've since
given up on it.
> Fix it in the C library or somewhere it doesn't harm the clueful
Can you give an example of a clueful package that makes
use of this feature and would be harmed if select() suddenly
became posix-compliant?
- Dan
next reply other threads:[~2002-07-20 3:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 3:59 dank [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-28 10:33 [PATCH] 'select' failure or signal should not update timeout linux
2002-07-21 3:34 Peter T. Breuer
[not found] <200207171430.g6HEUvY23619@aztec.santafe.edu>
2002-07-19 9:52 ` Paul Eggert
2002-07-20 0:38 ` Alan Cox
2002-07-20 5:57 ` Linus Torvalds
2002-07-21 15:36 ` Eric W. Biederman
2002-07-24 13:44 ` Jamie Lokier
2002-07-24 18:48 ` Linus Torvalds
2002-07-24 19:07 ` Chris Friesen
2002-07-24 23:30 ` Jamie Lokier
2002-07-25 6:32 ` Rusty Russell
2002-07-25 18:31 ` george anzinger
2002-07-28 5:40 ` David Schwartz
2002-07-25 16:35 ` Eric W. Biederman
2002-07-25 17:15 ` Jamie Lokier
2002-07-21 16:00 ` Christoph Rohland
2002-07-21 16:43 ` Linus Torvalds
2002-07-21 17:51 ` dean gaudet
2002-07-22 3:59 ` Edgar Toernig
2002-07-22 6:51 ` Christoph Rohland
2002-07-21 16:26 ` Ingo Molnar
2002-07-21 20:14 ` Richard Stallman
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=3D38E022.4005981E@kegel.com \
--to=dank@kegel.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.