From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 0/3] vfio: fixup notifiers and avoid possible deadlock
Date: Tue, 11 Jun 2013 10:01:37 -0600 [thread overview]
Message-ID: <20130611155848.9995.41709.stgit@bling.home> (raw)
Cleanup a couple of the notifier paths to remove bogus WARN_ON calls.
One is pretty easy to hit and neither really signifies a problems.
Fix remove path to avoid potential deadlock with other device_lock
holders. Thanks,
Alex
---
Alex Williamson (3):
vfio: Don't overreact to DEL_DEVICE
vfio: Ignore sprurious notifies
vfio-pci: Avoid deadlock on remove
drivers/vfio/pci/vfio_pci.c | 23 +++++++++++++++++++++--
drivers/vfio/vfio.c | 37 ++++++++++---------------------------
2 files changed, 31 insertions(+), 29 deletions(-)
next reply other threads:[~2013-06-11 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 16:01 Alex Williamson [this message]
2013-06-11 16:01 ` [PATCH 1/3] vfio: Don't overreact to DEL_DEVICE Alex Williamson
2013-06-11 16:01 ` [PATCH 2/3] vfio: Ignore sprurious notifies Alex Williamson
2013-06-11 16:01 ` [PATCH 3/3] vfio-pci: Avoid deadlock on remove Alex Williamson
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=20130611155848.9995.41709.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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