> On 11 Oct 2016, at 6:35, Cao jin <[email protected]> wrote: > > > >> On 10/06/2016 05:39 PM, Dmitry Fleytman wrote: >> > >> >> Hello, >> >> Yes, from what I see, this call is wrong and leads to >> reference leaks on device unload at migration target. >> It should be removed. >> >> Best regards, >> Dmitry >> > > Hi,Dmitry > > From what I saw, current code will call msix_vector_use twice on migration > target, which is wrong. I am not quite follow you on "reference leak", are > you saying the same thing as me? if not, could you help to explain more?
Hello, Yes, I meant exactly this :) msix_vector_use() increments vector reference counter each time it is called, so device holds two references to used vectors after migration. The second reference will be leaked because there is no second call to msix_vector_unuse() on unload. Best Regards, Dmitry > > -- > Yours Sincerely, > > Cao jin > >
