From: Jonas Blixt <jonas.blixt@actia.se>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <shuah@kernel.org>, <valentina.manea.m@gmail.com>,
<stern@rowland.harvard.edu>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] USB: usbip: fix stub_dev hub disconnect
Date: Thu, 15 Jun 2023 11:22:05 +0200 [thread overview]
Message-ID: <20230615092205.GA1212960@W388ANL> (raw)
In-Reply-To: <2023061347-reverse-staleness-e4f3@gregkh>
On Tue, Jun 13, 2023 at 11:50:31AM +0200, Greg KH wrote:
> On Tue, Jun 13, 2023 at 11:29:18AM +0200, Jonas Blixt wrote:
> > If a hub is disconnected that has device(s) that's attached to the usbip layer
> > the disconnect function might fail because it tries to release the port
> > on an already disconnected hub.
> >
> > Fixes: 6080cd0e9239 ("staging: usbip: claim ports used by shared devices")
> > Signed-off-by: Jonas Blixt <jonas.blixt@actia.se>
> > ---
> > drivers/usb/usbip/stub_dev.c | 8 ++++++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/usb/usbip/stub_dev.c b/drivers/usb/usbip/stub_dev.c
> > index 2305d425e6c9..257861787cdf 100644
> > --- a/drivers/usb/usbip/stub_dev.c
> > +++ b/drivers/usb/usbip/stub_dev.c
> > @@ -427,8 +427,12 @@ static void stub_disconnect(struct usb_device *udev)
> > /* release port */
> > rc = usb_hub_release_port(udev->parent, udev->portnum,
> > (struct usb_dev_state *) udev);
> > - if (rc) {
> > - dev_dbg(&udev->dev, "unable to release port\n");
> > + /*
> > + * NOTE: If a HUB disconnect triggered disconnect of the down stream
> > + * device usb_hub_release_port will return -ENODEV.
>
> How about adding, "so we can safely ignore that error here."
>
> thanks,
>
> greg k-h
Yes, I'll update the comment and prepare a V2 patch.
Jonas
prev parent reply other threads:[~2023-06-15 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 9:29 [PATCH] USB: usbip: fix stub_dev hub disconnect Jonas Blixt
2023-06-13 9:50 ` Greg KH
2023-06-15 9:22 ` Jonas Blixt [this message]
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=20230615092205.GA1212960@W388ANL \
--to=jonas.blixt@actia.se \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=stern@rowland.harvard.edu \
--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