From: Shuah Khan <skhan@linuxfoundation.org>
To: Anirudh Rayabharam <mail@anirudhrb.com>,
valentina.manea.m@gmail.com, shuah@kernel.org,
gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 1/2] usbip: give back URBs for unsent unlink requests during cleanup
Date: Mon, 23 Aug 2021 16:20:34 -0600 [thread overview]
Message-ID: <8fe11b13-58b4-e696-1727-6bd8226b67f9@linuxfoundation.org> (raw)
In-Reply-To: <20210820190122.16379-2-mail@anirudhrb.com>
On 8/20/21 1:01 PM, Anirudh Rayabharam wrote:
> In vhci_device_unlink_cleanup(), the URBs for unsent unlink requests are
> not given back. This sometimes causes usb_kill_urb to wait indefinitely
> for that urb to be given back. syzbot has reported a hung task issue [1]
> for this.
>
> To fix this, give back the urbs corresponding to unsent unlink requests
> (unlink_tx list) similar to how urbs corresponding to unanswered unlink
> requests (unlink_rx list) are given back.
>
> [1]: https://syzkaller.appspot.com/bug?id=08f12df95ae7da69814e64eb5515d5a85ed06b76
>
> Reported-by: syzbot+74d6ef051d3d2eacf428@syzkaller.appspotmail.com
> Tested-by: syzbot+74d6ef051d3d2eacf428@syzkaller.appspotmail.com
> Signed-off-by: Anirudh Rayabharam <mail@anirudhrb.com>
> ---
> drivers/usb/usbip/vhci_hcd.c | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/drivers/usb/usbip/vhci_hcd.c b/drivers/usb/usbip/vhci_hcd.c
> index 4ba6bcdaa8e9..190bd3d1c1f0 100644
> --- a/drivers/usb/usbip/vhci_hcd.c
> +++ b/drivers/usb/usbip/vhci_hcd.c
> @@ -957,8 +957,32 @@ static void vhci_device_unlink_cleanup(struct vhci_device *vdev)
> spin_lock(&vdev->priv_lock);
>
> list_for_each_entry_safe(unlink, tmp, &vdev->unlink_tx, list) {
> + struct urb *urb;
> +
> + /* give back urb of unsent unlink request */
> pr_info("unlink cleanup tx %lu\n", unlink->unlink_seqnum);
> +
> + urb = pickup_urb_and_free_priv(vdev, unlink->unlink_seqnum);
> + if (!urb) {
> + list_del(&unlink->list);
> + kfree(unlink);
> + continue;
> + }
> +
> + urb->status = -ENODEV;
> +
> + usb_hcd_unlink_urb_from_ep(hcd, urb);
> +
> list_del(&unlink->list);
> +
> + spin_unlock(&vdev->priv_lock);
> + spin_unlock_irqrestore(&vhci->lock, flags);
> +
> + usb_hcd_giveback_urb(hcd, urb, urb->status);
> +
> + spin_lock_irqsave(&vhci->lock, flags);
> + spin_lock(&vdev->priv_lock);
> +
> kfree(unlink);
> }
>
>
Looks good.
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2021-08-23 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 19:01 [PATCH v4 0/2] Fix syzkaller bug: hung task in hub_port_init Anirudh Rayabharam
2021-08-20 19:01 ` [PATCH v4 1/2] usbip: give back URBs for unsent unlink requests during cleanup Anirudh Rayabharam
2021-08-23 22:20 ` Shuah Khan [this message]
2021-08-20 19:01 ` [PATCH v4 2/2] usbip: clean up code in vhci_device_unlink_cleanup Anirudh Rayabharam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8fe11b13-58b4-e696-1727-6bd8226b67f9@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=shuah@kernel.org \
--cc=valentina.manea.m@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®