From: Kevin Wolf <kwolf@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, avi@redhat.com, kvm@vger.kernel.org,
aliguori@us.ibm.com
Subject: Re: [PATCH 1/2] fix segfault in msix_save
Date: Wed, 01 Jul 2009 14:27:17 +0200 [thread overview]
Message-ID: <4A4B5625.7040407@redhat.com> (raw)
In-Reply-To: <20090701115014.GB16726@redhat.com>
Michael S. Tsirkin schrieb:
> This fixes segfault reported by Kevin Wolf,
> and simplifies the code in msix_save.
>
> Reported-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
I can confirm that this fixes the segfault for me.
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH 1/2] fix segfault in msix_save
Date: Wed, 01 Jul 2009 14:27:17 +0200 [thread overview]
Message-ID: <4A4B5625.7040407@redhat.com> (raw)
In-Reply-To: <20090701115014.GB16726@redhat.com>
Michael S. Tsirkin schrieb:
> This fixes segfault reported by Kevin Wolf,
> and simplifies the code in msix_save.
>
> Reported-by: Kevin Wolf <kwolf@redhat.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
I can confirm that this fixes the segfault for me.
Kevin
next prev parent reply other threads:[~2009-07-01 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1246448461.git.mst@redhat.com>
2009-07-01 11:50 ` [PATCH 1/2] fix segfault in msix_save Michael S. Tsirkin
2009-07-01 11:50 ` [Qemu-devel] " Michael S. Tsirkin
2009-07-01 12:08 ` Michael S. Tsirkin
2009-07-01 12:27 ` Kevin Wolf [this message]
2009-07-01 12:27 ` [Qemu-devel] " Kevin Wolf
2009-07-01 11:50 ` [PATCH 2/2] qemu: fix up load for msi-x Michael S. Tsirkin
2009-07-01 11:50 ` [Qemu-devel] " Michael S. Tsirkin
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=4A4B5625.7040407@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@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 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.