> -----Original Message----- > From: Greg KH [mailto:[email protected]] > Sent: Monday, September 18, 2017 7:00 AM > To: KY Srinivasan <[email protected]> > Cc: [email protected]; [email protected]; > [email protected]; [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected]; Stephen Hemminger > <[email protected]>; Haiyang Zhang <[email protected]> > Subject: Re: [PATCH V2 1/4] vmbus: don't acquire the mutex in > vmbus_hvsock_device_unregister() > > On Sun, Sep 17, 2017 at 08:54:16PM -0700, [email protected] > wrote: > > From: Dexuan Cui <[email protected]> > > > > Due to commit 54a66265d675 ("Drivers: hv: vmbus: Fix rescind handling"), > > we need this patch to resolve the below deadlock: > > > > after we get the mutex in vmbus_hvsock_device_unregister() and call > > vmbus_device_unregister() -> device_unregister() -> ... -> > device_release() > > -> vmbus_device_release(), we'll get a deadlock, because > > vmbus_device_release() tries to get the same mutex. > > > > Signed-off-by: Dexuan Cui <[email protected]> > > Cc: K. Y. Srinivasan <[email protected]> > > Cc: Haiyang Zhang <[email protected]> > > Cc: Stephen Hemminger <[email protected]> > > Signed-off-by: K. Y. Srinivasan <[email protected]> > > As every one of these patches had questions from me, please break them > up into different series, one for 4.14-final, and one for 4.15-rc1.
Will do. Thanks, K. Y > > thanks, > > greg k-h _______________________________________________ devel mailing list [email protected] http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
