From: Justin Chen <justin.chen@broadcom.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch,
bcm-kernel-feedback-list@broadcom.com,
florian.fainelli@broadcom.com, opendmb@gmail.com, nb@tipi-net.de
Subject: Re: [PATCH net 2/2] net: bcmgenet: fix racing timeout handler
Date: Tue, 31 Mar 2026 16:15:39 -0700 [thread overview]
Message-ID: <3550c9fb-2774-42ad-876c-cd6649fe0bc8@broadcom.com> (raw)
In-Reply-To: <20260327211331.78476a99@kernel.org>
On 3/27/26 9:13 PM, Jakub Kicinski wrote:
> On Thu, 26 Mar 2026 11:45:29 -0700 justin.chen@broadcom.com wrote:
>> The bcmgenet_timeout handler tries to take down all tx queues when
>> a single queue times out. This is over zealous and causes many race
>> conditions with queues that are still chugging along. Instead lets
>> only restart the timed out queue.
>
> FWIW AI seems to suggest we should also stop NAPI and the DMA in this
> case, just to make sure that the queue in question doesn't suddenly
> wake up either. Which seems fair but probably as a follow up and only
> if not too hard in itself..
Yea this crossed my mind. I was thinking we might need to grab the ring
lock here in case we race on the napi tx relcaim. But in my testing, I
wasn't able to reproduce the lock up with these changes as is. But might
be worth throwing a lock in there anyways. I don't think we need to halt
the DMA, since we clean up everything, worst outcome is a packet gets
sent out when we tag it as being dropped.
Thanks,
Justin
prev parent reply other threads:[~2026-03-31 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 18:45 [PATCH 0/2 net] net: bcmgenet: fix lock up when queues time out justin.chen
2026-03-26 18:45 ` [PATCH net 1/2] net: bcmgenet: fix leaking free_bds justin.chen
2026-03-28 4:11 ` Jakub Kicinski
2026-03-31 23:11 ` Justin Chen
2026-03-26 18:45 ` [PATCH net 2/2] net: bcmgenet: fix racing timeout handler justin.chen
2026-03-28 4:13 ` Jakub Kicinski
2026-03-31 23:15 ` Justin Chen [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=3550c9fb-2774-42ad-876c-cd6649fe0bc8@broadcom.com \
--to=justin.chen@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=opendmb@gmail.com \
--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