From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Marc Olberding <molberding@nvidia.com>,
openbmc@lists.ozlabs.org, joel@jms.id.au
Subject: Re: [PATCH] net: mctp: Fix tx queue stall
Date: Mon, 24 Nov 2025 16:05:59 +1030 [thread overview]
Message-ID: <88585442dc88144d0cb0e46bdcac161f8baa71c4.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251121-mctpusb-backport-v1-1-e53b4c80e06c@nvidia.com>
Hi Marc,
On Fri, 2025-11-21 at 12:29 -0800, Marc Olberding wrote:
> From: Jinliang Wang <jinliangw@google.com>
>
> The tx queue can become permanently stuck in a stopped state due to a
> race condition between the URB submission path and its completion
> callback.
>
> The URB completion callback can run immediately after usb_submit_urb()
> returns, before the submitting function calls netif_stop_queue(). If
> this occurs, the queue state management becomes desynchronized, leading
> to a stall where the queue is never woken.
>
> Fix this by moving the netif_stop_queue() call to before submitting the
> URB. This closes the race window by ensuring the network stack is aware
> the queue is stopped before the URB completion can possibly run.
>
> (cherry picked from commit da2522df3fcc6f57068470cbdcd6516d9eb76b37)
Interesting that this hasn't yet come in via stable, but oh well.
>
> Fixes: 0791c0327a6e ("net: mctp: Add MCTP USB transport driver")
> Signed-off-by: Jinliang Wang <jinliangw@google.com>
> Acked-by: Jeremy Kerr <jk@codeconstruct.com.au>
> Link: https://patch.msgid.link/20251027065530.2045724-1-jinliangw@google.com
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> Backports a fix from net-next to openbmc 6.12 for a race condition
> in the mctp-usb driver that results in an effective deadlock.
> This was seen to fix issues on the nvl32-obmc model with pldm
> firmware update
>
> Signed-off-by: Marc Olberding <molberding@nvidia.com>
Just a quick note that because you've put this below the --- mark git
drops it when the patch is applied. You need to put your tag in the
trailer section above, under Jakub's S-o-b tag.
See [1] for a bit of a formalisation of it all.
Andrew
[1]: https://git-scm.com/docs/git-interpret-trailers
prev parent reply other threads:[~2025-11-24 5:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 20:29 [PATCH] net: mctp: Fix tx queue stall Marc Olberding
2025-11-24 5:35 ` Andrew Jeffery [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=88585442dc88144d0cb0e46bdcac161f8baa71c4.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=molberding@nvidia.com \
--cc=openbmc@lists.ozlabs.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