From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>
Cc: linux-usb@vger.kernel.org, Josef Bacik <josef@toxicpanda.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] USB: serial: garmin_gps: fix deadlock on reset request
Date: Thu, 29 Oct 2026 14:54:11 +0100 [thread overview]
Message-ID: <2026102958-figurine-unthawed-e1c2@gregkh> (raw)
In-Reply-To: <20261029101828.865915-1-johan@kernel.org>
On Thu, Oct 29, 2026 at 11:18:28AM +0100, Johan Hovold wrote:
> The garmin_gps driver has a reset feature that is supposed to reset the
> device when writing a private reset request packet. The reset is however
> done synchronously from the write() callback (and without holding the
> required device lock) which leads to a deadlock in the line discipline
> when hanging up the port as part of disconnect.
>
> Switch to using the asynchronous reset interface while dropping the
> redundant and synchronous stopping of the interrupt urb (write()
> callbacks are supposed to be atomic and USB core, USB serial core and
> the driver itself will unlink and kill all URBs during disconnect).
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Reported-by: Josef Bacik <josef@toxicpanda.com>
> Link: https://lore.kernel.org/2026102733-prayer-drainer-56f3@gregkh
> Cc: stable@vger.kernel.org
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
> drivers/usb/serial/garmin_gps.c | 12 +++---------
> 1 file changed, 3 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/usb/serial/garmin_gps.c b/drivers/usb/serial/garmin_gps.c
> index abfc03e44ca9..f1e69eca2601 100644
> --- a/drivers/usb/serial/garmin_gps.c
> +++ b/drivers/usb/serial/garmin_gps.c
> @@ -823,10 +823,9 @@ static void priv_status_resp(struct usb_serial_port *port)
> * Garmin specific driver functions
> ******************************************************************************/
>
> -static int process_resetdev_request(struct usb_serial_port *port)
> +static void process_resetdev_request(struct usb_serial_port *port)
> {
> unsigned long flags;
> - int status;
> struct garmin_data *garmin_data_p = usb_get_serial_port_data(port);
>
> spin_lock_irqsave(&garmin_data_p->lock, flags);
> @@ -835,13 +834,8 @@ static int process_resetdev_request(struct usb_serial_port *port)
> garmin_data_p->serial_num = 0;
> spin_unlock_irqrestore(&garmin_data_p->lock, flags);
>
> - usb_kill_urb(port->interrupt_in_urb);
> - dev_dbg(&port->dev, "%s - usb_reset_device\n", __func__);
> - status = usb_reset_device(port->serial->dev);
> - if (status)
> - dev_dbg(&port->dev, "%s - usb_reset_device failed: %d\n",
> - __func__, status);
> - return status;
> + dev_dbg(&port->dev, "%s - usb_queue_reset_device\n", __func__);
> + usb_queue_reset_device(port->serial->interface);
> }
>
>
> --
> 2.55.0
>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2026-10-29 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 10:18 [PATCH] USB: serial: garmin_gps: fix deadlock on reset request Johan Hovold
2026-10-29 10:28 ` sashiko-bot
2026-10-29 13:54 ` Greg Kroah-Hartman [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=2026102958-figurine-unthawed-e1c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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