RE: Re: Re: Re: Subject: [PATCH v1] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

2017-02-14 Thread Alan Stern
On Thu, 2 Feb 2017, Ajay Kaher wrote: >  At boot time, probe function of multiple connected devices >  (proprietary devices) execute simultaneously. > >>> > >>> What exactly do you mean here?  How can probe happen "simultaneously"? > >>> The USB core prevents this, right? > >>  > >> I 

RE: Re: Re: Re: Subject: [PATCH v1] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

2017-02-14 Thread Alan Stern
On Thu, 2 Feb 2017, Ajay Kaher wrote: >  At boot time, probe function of multiple connected devices >  (proprietary devices) execute simultaneously. > >>> > >>> What exactly do you mean here?  How can probe happen "simultaneously"? > >>> The USB core prevents this, right? > >>  > >> I 

RE: Re: Re: Re: Subject: [PATCH v1] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

2017-02-14 Thread Ajay Kaher
 At boot time, probe function of multiple connected devices  (proprietary devices) execute simultaneously. >>> >>> What exactly do you mean here?  How can probe happen "simultaneously"? >>> The USB core prevents this, right? >>  >> I have observed two scenarios to call probe function: >> 

RE: Re: Re: Re: Subject: [PATCH v1] USB:Core: BugFix: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously

2017-02-14 Thread Ajay Kaher
 At boot time, probe function of multiple connected devices  (proprietary devices) execute simultaneously. >>> >>> What exactly do you mean here?  How can probe happen "simultaneously"? >>> The USB core prevents this, right? >>  >> I have observed two scenarios to call probe function: >>