From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] audit needed for signal handlers
Date: Mon, 11 Nov 2013 18:05:51 +0100 [thread overview]
Message-ID: <52810E6F.1010505@redhat.com> (raw)
In-Reply-To: <CA+aC4kugrRczy5X=c797_YikXsNqCuruM2NaVfNeN-n6Oidnkg@mail.gmail.com>
Il 11/11/2013 17:56, Anthony Liguori ha scritto:
> On Mon, Nov 11, 2013 at 8:50 AM, Eric Blake <eblake@redhat.com> wrote:
>> Quick - identify the bug in this code (from ui/curses.c):
>>
>> static void curses_winch_handler(int signum)
>> {
>> struct winsize {
>> unsigned short ws_row;
>> unsigned short ws_col;
>> unsigned short ws_xpixel; /* unused */
>> unsigned short ws_ypixel; /* unused */
>> } ws;
>>
>> /* terminal size changed */
>> if (ioctl(1, TIOCGWINSZ, &ws) == -1)
>> return;
>>
>> resize_term(ws.ws_row, ws.ws_col);
>> curses_calc_pad();
>> invalidate = 1;
>>
>> /* some systems require this */
>> signal(SIGWINCH, curses_winch_handler);
>> }
>>
>> Here's a hint: ioctl() can clobber errno. But if a signal handler is
>> called in the middle of other code that is using errno, then the handler
>> MUST restore the value of errno before returning, if it is to guarantee
>> that the interrupted context won't be corrupted.
>
> Isn't this precisely why EINTR exists?
No.
do {
rc = read(...);
} while (rc == -1 && errno == EINTR);
/* signal handler runs here */
if (errno == EAGAIN) {
...
}
That said, aren't all signals in QEMU (except SIG_IPI) caught with
signalfd and the handlers run synchronously in the iothread?
Paolo
next prev parent reply other threads:[~2013-11-11 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 16:50 [Qemu-devel] audit needed for signal handlers Eric Blake
2013-11-11 16:56 ` Anthony Liguori
2013-11-11 17:03 ` Eric Blake
2013-11-11 17:05 ` Paolo Bonzini [this message]
2013-11-11 17:08 ` Eric Blake
2013-11-11 17:11 ` Paolo Bonzini
2013-11-11 17:13 ` Peter Maydell
2013-11-11 17:22 ` Eric Blake
2013-11-11 17:47 ` Paolo Bonzini
2013-11-12 8:18 ` Gerd Hoffmann
2013-11-12 12:07 ` Laszlo Ersek
2013-11-11 17:11 ` Peter Maydell
2013-11-11 18:03 ` Max Filippov
2013-11-12 12:24 ` Laszlo Ersek
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=52810E6F.1010505@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).