From: Florian Weimer <Florian.Weimer@RUS.Uni-Stuttgart.DE>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: I/O system call never returns if file desc is closed in the
Date: 07 Jun 2001 06:24:38 +0200 [thread overview]
Message-ID: <tgbso0diih.fsf@mercury.rus.uni-stuttgart.de> (raw)
In-Reply-To: <E157kxf-0000UE-00@the-village.bc.nu> <p05100310b744a22f02a6@[192.109.102.42]>
In-Reply-To: <p05100310b744a22f02a6@[192.109.102.42]> (Matthias Urlichs's message of "Thu, 7 Jun 2001 05:25:30 +0200")
Matthias Urlichs <smurf@noris.de> writes:
> Select is defined as to return, with the appropriate bit set, if/when
> a nonblocking read/write on the file descriptor won't block. You'd get
> EBADF in this case, therefore causing the select to return would be a
> Good Thing.
How do you avoid race conditions if more than one thread is creating
file descriptors? I think you can only do that under very special
circumstances, and it definitely requires some synchronization.
--
Florian Weimer Florian.Weimer@RUS.Uni-Stuttgart.DE
University of Stuttgart http://cert.uni-stuttgart.de/
RUS-CERT +49-711-685-5973/fax +49-711-685-5898
next prev parent reply other threads:[~2001-06-07 4:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-06 14:26 PROBLEM: I/O system call never returns if file desc is closed in the meantime thierry.lelegard
2001-06-06 21:35 ` PROBLEM: I/O system call never returns if file desc is closed in the Alan Cox
2001-06-07 3:25 ` Matthias Urlichs
2001-06-07 4:24 ` Florian Weimer [this message]
2001-06-07 4:43 ` Alexander Viro
2001-06-07 12:25 ` Florian Weimer
2001-06-07 15:33 ` Alexander Viro
2001-06-07 4:56 ` Alexander Viro
2001-06-07 6:06 ` Matthias Urlichs
2001-06-07 6:14 ` Alexander Viro
2001-06-07 22:14 ` 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=tgbso0diih.fsf@mercury.rus.uni-stuttgart.de \
--to=florian.weimer@rus.uni-stuttgart.de \
--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®