From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 30 Apr 2019 11:29:22 +0200 From: Halil Pasic Subject: Re: [PATCH v7 2/4] vfio: ap: register IOMMU VFIO notifier In-Reply-To: References: <1556283688-556-1-git-send-email-pmorel@linux.ibm.com> <1556283688-556-3-git-send-email-pmorel@linux.ibm.com> <20190429180702.641c9110.pasic@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20190430112922.0b0b90c5.pasic@linux.ibm.com> Sender: kvm-owner@vger.kernel.org List-Archive: List-Post: To: Pierre Morel Cc: borntraeger@de.ibm.com, alex.williamson@redhat.com, cohuck@redhat.com, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org, frankja@linux.ibm.com, akrowiak@linux.ibm.com, david@redhat.com, schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com, freude@linux.ibm.com, mimu@linux.ibm.com List-ID: On Tue, 30 Apr 2019 09:59:51 +0200 Pierre Morel wrote: > On 29/04/2019 18:07, Halil Pasic wrote: > > On Fri, 26 Apr 2019 15:01:26 +0200 > > Pierre Morel wrote: > > > >> @@ -858,7 +887,17 @@ static int vfio_ap_mdev_open(struct mdev_device *mdev) > >> return ret; > >> } > >> > >> - return 0; > >> + matrix_mdev->iommu_notifier.notifier_call = vfio_ap_mdev_iommu_notifier; > >> + events = VFIO_IOMMU_NOTIFY_DMA_UNMAP; > >> + ret = vfio_register_notifier(mdev_dev(mdev), VFIO_IOMMU_NOTIFY, > >> + &events, &matrix_mdev->iommu_notifier); > >> + if (!ret) > >> + return ret; > >> + > >> + vfio_unregister_notifier(mdev_dev(mdev), VFIO_GROUP_NOTIFY, > >> + &matrix_mdev->group_notifier); > >> + module_put(THIS_MODULE); > > > > Can you please explain this module_put() here? I don't see anything in > > the cover letter. > > May be you should have a look at the sources or the original patch > series of Tony, there is a try_module_get() at the beginning of open to > make sure that the module is not taken away while in use by the guest. > > In the case we failed to open the mediated device we let fall the reference. > Right, my bad. I did not notice we were on the error recovery path. Regards, Halil