From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/3] vfio: free data and unmap BARs in instance_finalize
Date: Sun, 08 Feb 2015 19:55:39 +0100 [thread overview]
Message-ID: <54D7B12B.7040600@redhat.com> (raw)
In-Reply-To: <1423416126.22865.668.camel@redhat.com>
On 08/02/2015 18:22, Alex Williamson wrote:
> Ok, I went back to 83761b9244ad, applied 3a4dbe6aa934 to get the
> object_unparent() fix, then applied this series. Everything seems to
> work ok. Then I manually applied and bisected the commits that came in
> via d5fbb4c9ed52. I land on 374f2981d1f1 as introducing the segfault in
> memory_listener_register(). I guess I was mis-remembering where I did
> my testing for the last vfio pull request. My tag was based on ec6f25e,
> but I remember that I had to test based on a commit before the RCU
> merge.
Ouch. memory_listeners needs mutex protection.
Paolo
prev parent reply other threads:[~2015-02-08 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 21:15 [Qemu-devel] [PATCH v3 0/3] vfio: free data and unmap BARs in instance_finalize Paolo Bonzini
2015-02-06 21:15 ` [Qemu-devel] [PATCH 1/3] vfio: cleanup vfio_get_device error path, remove vfio_populate_device callback Paolo Bonzini
2015-02-06 21:15 ` [Qemu-devel] [PATCH 2/3] vfio: free dynamically-allocated data in instance_finalize Paolo Bonzini
2015-02-06 21:15 ` [Qemu-devel] [PATCH 3/3] vfio: unmap and free BAR " Paolo Bonzini
2015-02-07 1:39 ` [Qemu-devel] [PATCH v3 0/3] vfio: free data and unmap BARs " Alex Williamson
2015-02-07 20:00 ` Paolo Bonzini
2015-02-08 17:22 ` Alex Williamson
2015-02-08 18:55 ` Paolo Bonzini [this message]
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=54D7B12B.7040600@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@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).