linux-kernel - Re: [syzbot] INFO: task hung in port100

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 25 Oct 2021 12:22:00 -0400
From:   Alan Stern <stern@...land.harvard.edu>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc:     Felipe Balbi <balbi@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        syzbot <syzbot+abd2e0dafb481b621869@...kaller.appspotmail.com>,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        syzkaller-bugs@...glegroups.com,
        Pavel Skripkin <paskripkin@...il.com>,
        Thierry Escande <thierry.escande@...labora.com>,
        Andrey Konovalov <andreyknvl@...il.com>
Subject: Re: [syzbot] INFO: task hung in port100_probe

On Mon, Oct 25, 2021 at 04:57:23PM +0200, Krzysztof Kozlowski wrote:
> On 21/10/2021 00:05, Alan Stern wrote:
> >>
> >> 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.

> 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.

> 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?  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.

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.

Alan Stern