Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-12 Thread Tejun Heo
Hello, On Mon, Dec 12, 2016 at 12:33:36PM -0600, Rob Herring wrote: > Maybe I'm confused, but don't you need this for all drivers? You need > sync the async SCSI scanning to the driver remove regardless of async > probe. The driver core synchronization is only for synchronizing the > remove with p

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-12 Thread Rob Herring
On Mon, Dec 12, 2016 at 11:50 AM, Tejun Heo wrote: > Hello, > > On Sun, Dec 11, 2016 at 03:44:36AM +0200, Vladimir Zapolskiy wrote: >> On 12/10/2016 03:04 PM, Greg Kroah-Hartman wrote: >> > Hm, how does this not also get hit if you unbind/bind/unbind/bind/etc. >> > from userspace as well? I don't

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-12 Thread Tejun Heo
Hello, On Sun, Dec 11, 2016 at 03:44:36AM +0200, Vladimir Zapolskiy wrote: > On 12/10/2016 03:04 PM, Greg Kroah-Hartman wrote: > > Hm, how does this not also get hit if you unbind/bind/unbind/bind/etc. > > from userspace as well? I don't think this is a > > CONFIG_DEBUG_TEST_DRIVER_REMOVE issue,

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-10 Thread Vladimir Zapolskiy
Hello Greg, I'm adding Tejun to the list of addressees. On 12/10/2016 03:04 PM, Greg Kroah-Hartman wrote: > On Sat, Dec 10, 2016 at 02:38:41PM +0200, Vladimir Zapolskiy wrote: >> Hello Greg, >> >> On 12/10/2016 09:32 AM, Greg Kroah-Hartman wrote: >>> On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vlad

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-10 Thread Greg Kroah-Hartman
On Sat, Dec 10, 2016 at 02:38:41PM +0200, Vladimir Zapolskiy wrote: > Hello Greg, > > On 12/10/2016 09:32 AM, Greg Kroah-Hartman wrote: > > On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vladimir Zapolskiy wrote: > >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false > >> positives

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-10 Thread Vladimir Zapolskiy
Hello Dmitry, On 12/10/2016 03:59 AM, Dmitry Torokhov wrote: > On Fri, Dec 9, 2016 at 4:15 PM, Vladimir Zapolskiy wrote: >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false >> positives are reported for ATA controller drivers, because ATA port >> probes are done asynchronous

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-10 Thread Vladimir Zapolskiy
Hello Greg, On 12/10/2016 09:32 AM, Greg Kroah-Hartman wrote: > On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vladimir Zapolskiy wrote: >> If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false >> positives are reported for ATA controller drivers, because ATA port >> probes are done as

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-09 Thread Greg Kroah-Hartman
On Sat, Dec 10, 2016 at 02:15:19AM +0200, Vladimir Zapolskiy wrote: > If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false > positives are reported for ATA controller drivers, because ATA port > probes are done asynchronously, and the same problem may also touch > other asynchrono

Re: [PATCH] driver core: flush async calls before testing driver removal

2016-12-09 Thread Dmitry Torokhov
On Fri, Dec 9, 2016 at 4:15 PM, Vladimir Zapolskiy wrote: > If CONFIG_DEBUG_TEST_DRIVER_REMOVE option is enabled a number of false > positives are reported for ATA controller drivers, because ATA port > probes are done asynchronously, and the same problem may also touch > other asynchronously prob