From: Alex Williamson <alex.williamson@redhat.com>
To: Matthew Rosato <mjrosato@linux.ibm.com>
Cc: "Liu, Yi L" <yi.l.liu@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"farman@linux.ibm.com" <farman@linux.ibm.com>,
"pmorel@linux.ibm.com" <pmorel@linux.ibm.com>,
"borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>,
"frankja@linux.ibm.com" <frankja@linux.ibm.com>,
"imbrenda@linux.ibm.com" <imbrenda@linux.ibm.com>,
"david@redhat.com" <david@redhat.com>,
"akrowiak@linux.ibm.com" <akrowiak@linux.ibm.com>,
"jjherne@linux.ibm.com" <jjherne@linux.ibm.com>,
"pasic@linux.ibm.com" <pasic@linux.ibm.com>,
"zhenyuw@linux.intel.com" <zhenyuw@linux.intel.com>,
"Wang, Zhi A" <zhi.a.wang@intel.com>, "Christopherson, ,
Sean" <seanjc@google.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] vfio: fix deadlock between group lock and kvm lock
Date: Fri, 3 Feb 2023 14:35:51 -0700 [thread overview]
Message-ID: <20230203143551.2f349702.alex.williamson@redhat.com> (raw)
In-Reply-To: <b5e64413-0374-edd8-9bfd-8bb613ab04f9@linux.ibm.com>
On Fri, 3 Feb 2023 16:19:10 -0500
Matthew Rosato <mjrosato@linux.ibm.com> wrote:
> > @@ -350,32 +350,25 @@ void vfio_device_get_kvm_safe(struct vfio_device *device)
> >
> > lockdep_assert_held(&device->dev_set->lock);
> >
> > - spin_lock(&device->group->kvm_ref_lock);
> > - if (!device->group->kvm)
> > - goto unlock;
> > -
> > pfn = symbol_get(kvm_put_kvm);
> > if (WARN_ON(!pfn))
> > - goto unlock;
> > + return;
> >
> > fn = symbol_get(kvm_get_kvm_safe);
> > if (WARN_ON(!fn)) {
> > symbol_put(kvm_put_kvm);
> > - goto unlock;
> > + return;
> > }
> > > ret = fn(device->group->kvm);
>
> s/device->group->kvm/kvm/
Oops, yes.
> With that small change, this looks good to me too (and testing looks
> good too). Do you want me to send a v4 for one last round of review?
Please do. Thanks,
Alex
next prev parent reply other threads:[~2023-02-03 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 16:24 [PATCH v3] vfio: fix deadlock between group lock and kvm lock Matthew Rosato
2023-02-02 19:42 ` Alex Williamson
2023-02-02 23:04 ` Tian, Kevin
2023-02-02 23:13 ` Alex Williamson
2023-02-03 2:00 ` Tian, Kevin
2023-02-03 13:32 ` Liu, Yi L
2023-02-03 13:49 ` Alex Williamson
2023-02-03 14:54 ` Liu, Yi L
2023-02-03 15:19 ` Alex Williamson
2023-02-03 17:29 ` Matthew Rosato
2023-02-03 20:35 ` Alex Williamson
2023-02-03 21:19 ` Matthew Rosato
2023-02-03 21:35 ` Alex Williamson [this message]
2023-02-03 8:58 ` Liu, Yi L
2023-02-03 14:26 ` Matthew Rosato
2023-02-03 14:48 ` Liu, Yi L
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=20230203143551.2f349702.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=jjherne@linux.ibm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=seanjc@google.com \
--cc=yi.l.liu@intel.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.a.wang@intel.com \
/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