From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Marian Krcmarik <mkrcmari@redhat.com>,
Alon Levy <alevy@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] monitor: Protect outbuf from concurrent access
Date: Thu, 01 Sep 2011 20:34:35 -0500 [thread overview]
Message-ID: <4E6032AB.8080804@codemonkey.ws> (raw)
In-Reply-To: <20110901163545.71ba1515@doriath>
On 09/01/2011 02:35 PM, Luiz Capitulino wrote:
> Sometimes, when having lots of VMs running on a RHEV host and the user
> attempts to close a SPICE window, libvirt will get corrupted json from
> QEMU.
>
> After some investigation, I found out that the problem is that different
> SPICE threads are calling monitor functions (such as
> monitor_protocol_event()) in parallel which causes concurrent access
> to the monitor's internal buffer outbuf[].
>
> This fixes the problem by protecting accesses to outbuf[] with a mutex.
>
> Honestly speaking, I'm not completely sure this the best thing to do
> because the monitor itself and other qemu subsystems are not thread safe,
> so having subsystems like SPICE assuming the contrary seems a bit
> catastrophic to me...
>
> Anyways, this commit fixes the problem at hand.
Nack.
This is absolutely a Spice bug. Spice should not be calling into QEMU
code from multiple threads. It should only call into QEMU code while
it's holding the qemu_mutex.
The right way to fix this is probably to make all of the
SpiceCoreInterface callbacks simply write to a file descriptor which can
then wake up QEMU to do the operation on behalf of it. It's ugly but
the libspice interface is far too tied to QEMU internals in the first
place which is the root of the problem.
Regards,
Anthony Liguori
>
> Signed-off-by: Luiz Capitulino<lcapitulino@redhat.com>
> ---
> monitor.c | 16 +++++++++++++++-
> 1 files changed, 15 insertions(+), 1 deletions(-)
>
> diff --git a/monitor.c b/monitor.c
> index 04f465a..61d4d93 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -57,6 +57,7 @@
> #include "json-parser.h"
> #include "osdep.h"
> #include "cpu.h"
> +#include "qemu-thread.h"
> #ifdef CONFIG_SIMPLE_TRACE
> #include "trace.h"
> #endif
> @@ -144,6 +145,7 @@ struct Monitor {
> int suspend_cnt;
> uint8_t outbuf[1024];
> int outbuf_index;
> + QemuMutex mutex;
> ReadLineState *rs;
> MonitorControl *mc;
> CPUState *mon_cpu;
> @@ -246,10 +248,14 @@ static int monitor_read_password(Monitor *mon, ReadLineFunc *readline_func,
>
> void monitor_flush(Monitor *mon)
> {
> + qemu_mutex_lock(&mon->mutex);
> +
> if (mon&& mon->outbuf_index != 0&& !mon->mux_out) {
> qemu_chr_fe_write(mon->chr, mon->outbuf, mon->outbuf_index);
> mon->outbuf_index = 0;
> }
> +
> + qemu_mutex_unlock(&mon->mutex);
> }
>
> /* flush at every end of line or if the buffer is full */
> @@ -257,6 +263,8 @@ static void monitor_puts(Monitor *mon, const char *str)
> {
> char c;
>
> + qemu_mutex_lock(&mon->mutex);
> +
> for(;;) {
> c = *str++;
> if (c == '\0')
> @@ -265,9 +273,14 @@ static void monitor_puts(Monitor *mon, const char *str)
> mon->outbuf[mon->outbuf_index++] = '\r';
> mon->outbuf[mon->outbuf_index++] = c;
> if (mon->outbuf_index>= (sizeof(mon->outbuf) - 1)
> - || c == '\n')
> + || c == '\n') {
> + qemu_mutex_unlock(&mon->mutex);
> monitor_flush(mon);
> + qemu_mutex_lock(&mon->mutex);
> + }
> }
> +
> + qemu_mutex_unlock(&mon->mutex);
> }
>
> void monitor_vprintf(Monitor *mon, const char *fmt, va_list ap)
> @@ -5275,6 +5288,7 @@ void monitor_init(CharDriverState *chr, int flags)
>
> mon = g_malloc0(sizeof(*mon));
>
> + qemu_mutex_init(&mon->mutex);
> mon->chr = chr;
> mon->flags = flags;
> if (flags& MONITOR_USE_READLINE) {
next prev parent reply other threads:[~2011-09-02 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 19:35 [Qemu-devel] [PATCH] monitor: Protect outbuf from concurrent access Luiz Capitulino
2011-09-01 19:47 ` Daniel P. Berrange
2011-09-01 21:03 ` Jan Kiszka
2011-09-02 1:34 ` Anthony Liguori [this message]
2011-09-02 9:41 ` Daniel P. Berrange
2011-09-02 11:26 ` Jan Kiszka
2011-09-02 13:39 ` Gerd Hoffmann
2011-09-02 14:03 ` Anthony Liguori
2011-09-02 14:24 ` Luiz Capitulino
2011-09-02 14:28 ` Anthony Liguori
2011-09-02 15:18 ` Gerd Hoffmann
2011-09-02 15:20 ` Anthony Liguori
2011-09-02 15:31 ` Paolo Bonzini
2011-09-02 15:37 ` Anthony Liguori
2011-09-05 7:48 ` Gerd Hoffmann
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=4E6032AB.8080804@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=alevy@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mkrcmari@redhat.com \
--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).