On Tue, Sep 19, 2017 at 7:17 PM, Alan Stern wrote:
> On Tue, 19 Sep 2017, Andrey Konovalov wrote:
>
>> On Fri, Sep 15, 2017 at 8:57 PM, Alan Stern
>> wrote:
>> > On Thu, 14 Sep 2017, Andrey Konovalov wrote:
>> >
>> >> On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern
>> >> wrote:
>> >> > On Thu, 14
On Tue, 19 Sep 2017, Andrey Konovalov wrote:
> On Fri, Sep 15, 2017 at 8:57 PM, Alan Stern wrote:
> > On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> >
> >> On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern
> >> wrote:
> >> > On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> >> >
> >> >> Looked at this a
On Fri, Sep 15, 2017 at 8:57 PM, Alan Stern wrote:
> On Thu, 14 Sep 2017, Andrey Konovalov wrote:
>
>> On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern
>> wrote:
>> > On Thu, 14 Sep 2017, Andrey Konovalov wrote:
>> >
>> >> Looked at this a little more.
>> >>
>> >> dummy_timer() stucks in an infinite
On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern wrote:
> > On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> >
> >> Looked at this a little more.
> >>
> >> dummy_timer() stucks in an infinite loop. It calls
> >> usb_hcd_giveback_urb(), which in turn calls u
On Thu, Sep 14, 2017 at 7:49 PM, Alan Stern wrote:
> On Thu, 14 Sep 2017, Andrey Konovalov wrote:
>
>> Looked at this a little more.
>>
>> dummy_timer() stucks in an infinite loop. It calls
>> usb_hcd_giveback_urb(), which in turn calls usbtouch_irq(), which
>> calls usb_submit_urb(), which calls
On Thu, 14 Sep 2017, Andrey Konovalov wrote:
> Looked at this a little more.
>
> dummy_timer() stucks in an infinite loop. It calls
> usb_hcd_giveback_urb(), which in turn calls usbtouch_irq(), which
> calls usb_submit_urb(), which calls dummy_urb_enqueue() and puts urb
> back into dummy urb queu
On Tue, Sep 12, 2017 at 7:44 PM, Andrey Konovalov wrote:
> On Tue, Sep 12, 2017 at 7:06 PM, Dmitry Torokhov
> wrote:
>> On Tue, Sep 12, 2017 at 05:48:51PM +0200, Andrey Konovalov wrote:
>>> On Mon, Sep 11, 2017 at 8:54 PM, Dmitry Torokhov
>>> wrote:
>>> > On Mon, Sep 11, 2017 at 8:15 AM, Andrey
On Tue, Sep 12, 2017 at 05:48:51PM +0200, Andrey Konovalov wrote:
> On Mon, Sep 11, 2017 at 8:54 PM, Dmitry Torokhov
> wrote:
> > On Mon, Sep 11, 2017 at 8:15 AM, Andrey Konovalov
> > wrote:
> >> On Mon, Sep 11, 2017 at 3:25 PM, Alan Stern
> >> wrote:
> >>> On Mon, 11 Sep 2017, Andrey Konovalo
On Mon, Sep 11, 2017 at 8:54 PM, Dmitry Torokhov
wrote:
> On Mon, Sep 11, 2017 at 8:15 AM, Andrey Konovalov
> wrote:
>> On Mon, Sep 11, 2017 at 3:25 PM, Alan Stern
>> wrote:
>>> On Mon, 11 Sep 2017, Andrey Konovalov wrote:
>>>
Hi!
I've been getting stall reports like this one wh
On Mon, Sep 11, 2017 at 8:15 AM, Andrey Konovalov wrote:
> On Mon, Sep 11, 2017 at 3:25 PM, Alan Stern wrote:
>> On Mon, 11 Sep 2017, Andrey Konovalov wrote:
>>
>>> Hi!
>>>
>>> I've been getting stall reports like this one while fuzzing the USB
>>> stack with gadgetfs. I'm wondering whether this
On Mon, Sep 11, 2017 at 3:25 PM, Alan Stern wrote:
> On Mon, 11 Sep 2017, Andrey Konovalov wrote:
>
>> Hi!
>>
>> I've been getting stall reports like this one while fuzzing the USB
>> stack with gadgetfs. I'm wondering whether this is a bug in gadgetfs
>> or is this report induced by the changes I
On Mon, 11 Sep 2017, Andrey Konovalov wrote:
> Hi!
>
> I've been getting stall reports like this one while fuzzing the USB
> stack with gadgetfs. I'm wondering whether this is a bug in gadgetfs
> or is this report induced by the changes I've made to the USB core
> code. I didn't touch gadgetfs co
Hi!
I've been getting stall reports like this one while fuzzing the USB
stack with gadgetfs. I'm wondering whether this is a bug in gadgetfs
or is this report induced by the changes I've made to the USB core
code. I didn't touch gadgetfs code though (except for adding a few
printk's).
I'm on comm
13 matches
Mail list logo