From: george@moberg.com
To: Tim Hockin <thockin@isunix.it.ilstu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Can EINTR be handled the way BSD handles it? -- a plea from a user-land
Date: Fri, 03 Nov 2000 14:44:17 -0500 [thread overview]
Message-ID: <3A031591.EA24ABFA@moberg.com> (raw)
In-Reply-To: <200011031841.MAA07209@isunix.it.ilstu.edu>
Tim Hockin wrote:
>
> > Considering that the threading library for Linux uses signals to make it
> > work, would it be possible to change the Linux kernel to operate the way
> > BSD does--instead of returning EINTR, just restart the interrupted
> > primitive?
>
> man sigaction, look for SA_RESTART
Thanks for the info.
After looking at it, let me modify my position a bit.
My problem is that pthread_create (glibc 2.1.3, kernel 2.2.17 i686) is
failing because, deep inside glibc somewhere, nanosleep() is returning
EINTR.
My code is not using signals. The threading library is, and there is
obviously some subtle bug going on here. Ever wonder why when browsing
with Netscape and you click on a link and it says "Interrupted system
call."? This is it. I'm arguing that the default behaviour should be
SA_RESTART, and if some programmer is so studly that they actually know
what the hell they are doing by disabling SA_RESTART, then they can do
it explicitly.
I don't mean this to sound like a rant. It's just that I can't possibly
ascertain why someone in their right mind would want any behaviour
different than SA_RESTART.
--
George T. Talbot
<george at moberg dot com>
-
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 parent reply other threads:[~2000-11-03 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200011031841.MAA07209@isunix.it.ilstu.edu>
2000-11-03 19:44 ` george [this message]
2000-11-03 21:27 ` Can EINTR be handled the way BSD handles it? -- a plea from a user-land H. Peter Anvin
2000-11-04 4:23 ` Theodore Y. Ts'o
2000-11-06 14:05 ` George Talbot
2000-11-06 15:30 ` Davide Libenzi
2000-11-06 17:50 ` Can EINTR be handled the way BSD handles it? -- a plea from a Tim Hockin
2000-11-06 14:17 ` Can EINTR be handled the way BSD handles it? -- a plea from a user-land George Talbot
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=3A031591.EA24ABFA@moberg.com \
--to=george@moberg.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@isunix.it.ilstu.edu \
/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;
as well as URLs for NNTP newsgroup(s).