From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Jinliang Wang <jinliangw@google.com>,
Matt Johnston <matt@codeconstruct.com.au>,
netdev@vger.kernel.org
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] net: mctp: Fix tx queue stall
Date: Mon, 27 Oct 2025 14:41:59 +0800 [thread overview]
Message-ID: <a24255faaf750bad30adefa24b510d0ccbaf37b0.camel@codeconstruct.com.au> (raw)
In-Reply-To: <20251025054452.1220262-1-jinliangw@google.com>
Hi Jinliang,
Thanks for the fix! A couple of comments on the metadata:
> Subject: [PATCH v2] net: mctp: Fix tx queue stall
You'll want to indicate that this is for net rather than net-next in
the subject prefix, so:
> Subject: [PATCH net v2] net: mctp: Fix tx queue stall
Then, since we're targeting net, we'll want a fixes tag too. I would
suggest:
Fixes: 0791c0327a6e ("net: mctp: Add MCTP USB transport driver")
- so we get appropriate backports. No need to reply to the original
message for subsequent versions either, a new thread is best.
Also, it's helpful to indicate changes between submitted versions,
under the '---' marker, which doesn't end up in the git commit.
Something like:
---
v3:
- target net tree, add fixes tag
v2:
- remove duplicate comment in commit message
---
drivers/net/mctp/mctp-usb.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
> 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.
LGTM. With the changes above:
Acked-by: Jeremy Kerr <jk@codeconstruct.com.au>
Cheers,
Jeremy
prev parent reply other threads:[~2025-10-27 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 5:30 [PATCH] net: mctp: Fix tx queue stall Jinliang Wang
2025-10-25 5:44 ` [PATCH v2] " Jinliang Wang
2025-10-27 6:41 ` Jeremy Kerr [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=a24255faaf750bad30adefa24b510d0ccbaf37b0.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jinliangw@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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