From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: drepper@cygnus.com
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>,
George Talbot <george@brain.moberg.com>,
Marc Lehmann <pcg@goof.com>,
linux-kernel@vger.kernel.org
Subject: Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer...
Date: Tue, 7 Nov 2000 10:53:23 -0500 [thread overview]
Message-ID: <200011071553.KAA21829@tsx-prime.MIT.EDU> (raw)
In-Reply-To: Ulrich Drepper's message of 06 Nov 2000 10:50:37 -0800, <m33dh5aq9u.fsf@otr.mynet.cygnus.com>
From: Ulrich Drepper <drepper@redhat.com>
Date: 06 Nov 2000 10:50:37 -0800
> Arguably though the bug is in glibc, in that if it's using signals
> behinds the scenes, it should have passed SA_RESTART to sigaction.
Why are you talking such a nonsense?
The claim was made that pthreads was using signals behind the scenes, so
that programs which weren't expecting that system calls to get
interrupted were getting interrupted. Hence, one could make the
argument that if the pthreads code had used SA_RESTART to set up its
signal handlers, then this situation wouldn't have come up.
I haven't looked more deeply into this. As far as I'm concerned,
threads === "more rope" and use of threads should be avoided whenever
possible, even if Linux had a decent threads implementation....
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-07 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001105042410.C3961@fuji.laendle>
2000-11-06 14:13 ` Can EINTR be handled the way BSD handles it? -- a plea from a user-land programmer George Talbot
2000-11-06 16:55 ` Theodore Y. Ts'o
2000-11-06 18:50 ` Ulrich Drepper
2000-11-06 19:11 ` Ulrich Drepper
2000-11-06 19:37 ` kuznet
2000-11-07 15:53 ` Theodore Y. Ts'o [this message]
2000-11-07 4:46 ` dean gaudet
2000-11-04 3:06 David Feuer
-- strict thread matches above, loose matches on Subject: below --
2000-11-03 19:29 george
2000-11-03 19:41 ` Ulrich Drepper
2000-11-03 19:49 ` george
2000-11-03 21:34 ` dean gaudet
2000-11-03 19:51 ` kuznet
2000-11-03 21:24 ` H. Peter Anvin
2000-11-03 20:20 ` Richard B. Johnson
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=200011071553.KAA21829@tsx-prime.MIT.EDU \
--to=tytso@mit.edu \
--cc=drepper@cygnus.com \
--cc=george@brain.moberg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcg@goof.com \
/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.