From: Andreas Schwab <schwab@suse.de>
To: "Phil Endecott" <phil_wueww_endecott@chezphil.org>
Cc: "Jiri Slaby" <jirislaby@gmail.com>,
<linux-kernel@vger.kernel.org>,
" Frederik Deweerdt" <deweerdt@free.fr>
Subject: Re: strace, accept(), ERESTARTSYS and EINTR
Date: Sat, 05 Jan 2008 17:38:34 +0100 [thread overview]
Message-ID: <jed4sgjkhh.fsf@sykes.suse.de> (raw)
In-Reply-To: <1199543075452@dmwebmail.japan.chezphil.org> (Phil Endecott's message of "Sat\, 05 Jan 2008 14\:24\:35 +0000")
"Phil Endecott" <phil_wueww_endecott@chezphil.org> writes:
> However, there's a lot of code and I know that there are bugs in it. I
> just want to focus on the kernel-related issue that the strace fragment
> that I posted brings up: even if my user code gets completely screwed up
> (corrupts its stack, runs out of FDs/VM/threads etc), I don't think that I
> should see in the strace output that accept() has returned
> ERESTARTSYS.
strace always sees the raw return value, before the signal handler is
executed and before the check for syscall restart is done.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-01-05 16:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 21:01 Phil Endecott
2008-01-04 22:55 ` Jiri Slaby
2008-01-04 23:52 ` Phil Endecott
2008-01-05 1:06 ` Frederik Deweerdt
2008-01-05 1:38 ` Phil Endecott
2008-01-05 10:31 ` Jiri Slaby
2008-01-05 11:33 ` Jiri Slaby
2008-01-05 14:24 ` Phil Endecott
2008-01-05 16:38 ` Andreas Schwab [this message]
2008-01-05 18:18 ` Phil Endecott
2008-01-05 19:19 ` Andreas Schwab
2008-01-05 19:35 ` Phil Endecott
2008-01-05 19:50 ` Andreas Schwab
2008-01-05 15:03 ` Andi Kleen
2008-01-05 17:02 ` Jiri Slaby
2008-01-05 18:42 ` Phil Endecott
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=jed4sgjkhh.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=deweerdt@free.fr \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phil_wueww_endecott@chezphil.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®