From: Anthony Liguori <anthony@codemonkey.ws>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] suppress 'warn_unused_result' warning
Date: Sun, 10 May 2009 18:19:34 -0500 [thread overview]
Message-ID: <4A076106.1010100@codemonkey.ws> (raw)
In-Reply-To: <20090510221500.GA27879@miranda.arrow>
Stuart Brady wrote:
> On Mon, May 11, 2009 at 03:15:11AM +0800, Chih-Min Chao wrote:
>
>> The patch add error handling to functions with 'warn_unused_result' return
>> value such as write, read, ftruncate, and realpath.
>>
>
> I'm slightly concerned -- read(), write() and ftruncate() can fail with
> EINTR if a signal is received at an unfortunate time, can't they?
>
> Do we mitigate this for the most part, somehow?
>
> Do kernels try to avoid this behaviour? If so, under what circumstances
> might EINTR still be returned?
>
EINTR is rather unfortunate. A lot of libraries don't handle it well,
for instance.
One the IO thread stabilizes and we can enable it by default, we'll be
able to eliminate signaling in the IO thread and thereby eliminate all
of the potentially buggy EINTR handling.
I think that's the best path forward.
NB we would still send the TCG thread signals to break it out of
execution but the TCG thread should not generally be doing system calls.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-05-10 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-10 19:15 [Qemu-devel] [PATCH] suppress 'warn_unused_result' warning Chih-Min Chao
2009-05-10 22:11 ` Paul Brook
2009-05-10 22:15 ` Stuart Brady
2009-05-10 23:19 ` Anthony Liguori [this message]
2009-05-11 1:53 ` M. Warner Losh
2009-05-11 15:42 ` Stuart Brady
2009-05-11 16:02 ` Paul Brook
2009-05-11 16:16 ` Anthony Liguori
2009-05-11 16:25 ` Daniel P. Berrange
2009-05-11 16:57 ` Anthony Liguori
2009-05-12 12:19 ` Jamie Lokier
2009-05-11 17:02 ` Jamie Lokier
2009-05-11 16:15 ` Daniel P. Berrange
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=4A076106.1010100@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=sdbrady@ntlworld.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 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).