From: Anthony Liguori <anthony@codemonkey.ws>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: qemu-devel@nongnu.org, Matthew Bloch <matthew@bytemark.co.uk>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix freezing bug in curses console
Date: Fri, 27 Feb 2009 15:04:01 -0600 [thread overview]
Message-ID: <49A85541.7040805@codemonkey.ws> (raw)
In-Reply-To: <fb249edb0902271301p6abf72fah4dd63497df052dd3@mail.gmail.com>
andrzej zaborowski wrote:
> 2009/2/27 Anthony Liguori <aliguori@us.ibm.com>:
>
>> Matthew Bloch wrote:
>>
>>> Hi there,
>>>
>>> We are running lots of kvm processes in screen and found that about 1 in
>>> 5 froze shortly after startup startup with a backtrace like this one:
>>>
>>> #0 0xf7c7fcd9 in pthread_exit () from /lib/tls/libc.so.6
>>> #1 0xf7cfbe62 in wresize () from /lib/libncurses.so.5
>>> #2 0xf7cfb7ab in is_term_resized () from /lib/libncurses.so.5
>>> #3 0xf7cfb877 in is_term_resized () from /lib/libncurses.so.5
>>> #4 0xf7cfba31 in resize_term () from /lib/libncurses.so.5
>>> #5 0x080d3dd9 in vga_init ()
>>> #6 <signal handler called>
>>> #7 0xf7c0da5b in free () from /lib/tls/libc.so.6
>>> #8 0xf7c0effe in calloc () from /lib/tls/libc.so.6
>>> #9 0xf7cf222e in newpad () from /lib/libncurses.so.5
>>> #10 0x080d3549 in vga_init ()
>>>
>>> We're just using the lenny version of kvm from 2008-12-16.
>>>
>>> On casual inspection, the SIGWINCH signal handling looked ropey to me -
>>> grandpa always told me not to do any real work in a signal handler, and
>>> the backtrace suggested re-entrancy problems in curses, so I changed the
>>> behaviour to set a flag and do the work in the main loop instead. Maybe
>>> I'm reading the backtrace wrong.
>>>
>>> So far that means that when you resize the window, the display is
>>> corrupt until the VM outputs some text, or the user hits a key. But I
>>> think it has solved the freezing / crashing bug too - would appreciate
>>> any comments on my analysis or proposed solution.
>>>
>>>
>> It's racy with select(). A better fix would be to create a pipe and write
>> to that pipe in the SIGWINCH handler. You should then register an io
>> callback using qemu_set_fd_handler2() that does the actions for SIGWINCH.
>>
>
> Maybe a bottom half would work? The scheduling of a bh shouldn't
> constitute "real work".
>
I think it still suffers from the same race condition so today it
wouldn't work. You could fix the bottom half scheduling though so that
you could safely schedule a bottom half from a signal handler (using
roughly the same trick).
Regards,
Anthony Liguori
> Cheers
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-02-27 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 15:51 [PATCH] Fix freezing bug in curses console Matthew Bloch
2009-02-27 19:49 ` Anthony Liguori
2009-02-27 21:01 ` [Qemu-devel] " andrzej zaborowski
2009-02-27 21:04 ` Anthony Liguori [this message]
2009-02-28 21:21 ` Jamie Lokier
2009-03-01 11:36 ` Daniel P. Berrange
2009-03-01 13:03 ` Paul Brook
2009-03-01 14:07 ` Anthony Liguori
2009-03-02 16:57 ` Jamie Lokier
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=49A85541.7040805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=balrogg@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=matthew@bytemark.co.uk \
--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 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.