Re: [syzbot] INFO: task hung in port100_probe

On 25/10/2021 18:22, Alan Stern wrote:

On Mon, Oct 25, 2021 at 04:57:23PM +0200, Krzysztof Kozlowski wrote:

quoted

On 21/10/2021 00:05, Alan Stern wrote:

quoted

quoted

The syzkaller reproducer fails if >1 of threads are running these usb
gadgets.  When this happens, no "in_urb" completion happens. No this
"ack" port100_recv_ack().

I added some debugs and simply dummy_hcd dummy_timer() is woken up on
enqueuing in_urb and then is looping crazy on a previous URB (some older
URB, coming from before port100 driver probe started). The dummy_timer()
loop never reaches the second "in_urb" to process it, I think.

Is there any way you can track down what's happening in that crazy loop?  
That is, what driver was responsible for the previous URB?

We have seen this sort of thing before, where a driver submits an URB 
for a gadget which has disconnected.  The URB fails with -EPROTO status 
but the URB's completion handler does an automatic resubmit.  That can 
lead to a very tight loop with dummy-hcd, and it could easily prevent 
some other important processing from occurring.  The simple solution is 
to prevent the driver from resubmitting when the completion status is 
-EPROTO.

Hi Alan,

Thanks for the reply.

The URB which causes crazy loop is the port100 driver second URB, the
one called ack or in_urb.

The flow is:
1. probe()
2. port100_get_command_type_mask()
3. port100_send_cmd_async()
4. port100_send_frame_async()
5. usb_submit_urb(dev->out_urb)
   The call succeeds, the dummy_hcd picks it up and immediately ends the
timer-loop with -EPROTO

So that URB completes immediately.

quoted

The completion here does not resubmit another/same URB. I checked this
carefully and I hope I did not miss anything.

Yeah, I see the same thing.

quoted

6. port100_submit_urb_for_ack() which sends the in_urb:
   usb_submit_urb(dev->in_urb)
... wait for completion
... dummy_hcd loops on this URB around line 2000:
if (status == -EINPROGRESS)
  continue

Do I understand this correctly?  You're saying that dummy-hcd executes 
the following jump at line 1975:

		/* incomplete transfer? */
		if (status == -EINPROGRESS)
			continue;

which goes back up to the loop head on line 1831:

	list_for_each_entry_safe(urbp, tmp, &dum_hcd->urbp_list, urbp_list) {

Is that right?

Yes, exactly. The loop continues, iterating over list finishes thus the
loops and dummy timer function exits. Then immediately it is being
rescheduled by something (I don't know by what yet).

To remind - the syzbot reproducer must run at least two threads
(spawning USB gadgets so creating separate dummy devices) at the same
time. However only one of dummy HCD devices seems to timer-loop
endlessly... but this might not be important, e.g. maybe it's how syzbot
reproducer works.

 I don't see why this should cause any problem.  It won't 
loop back to the same URB; it will make its way through the list.  
(Unless the list has somehow gotten corrupted...)  dum_hcd->urbp_list 
should be short (perhaps 32 entries at most), so the loop should reach 
the end of the list fairly quickly.

The list has actually only one element - only this one URB coming from
port100 device (which I was always calling second URB/ack, in_urb).

Now, doing all this 1000 times per second could use up a significant 
portion of the available time.  Do you think that's the reason for the 
problem?  It seems pretty unlikely.

No, this timer-looping itself is not a problem. Problem is that this URB
never reaches some final state, e.g. -EPROTO.

In normal operation, e.g. when reproducer did not hit the issue, both
URBs from port100 (the first out_urb and second in_urb) complete with
-EPROTO. In the case leading to hang ("task kworker/0:0:5 blocked for
more than 143 seconds"), the in_urb does not complete therefore the
port100 driver waits.

Whether this intensive timer-loop is important (processing the same URB
and continuing), I don't know.

Best regards,
Krzysztof