The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>,
	 "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	 Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	 Florian Westphal <fw@strlen.de>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com, stable@vger.kernel.org
Subject: Re: [PATCH net] net: fix spurious TX timeout after dev_activate()
Date: Tue, 25 Aug 2026 03:36:32 -0700	[thread overview]
Message-ID: <ao1bBrMlSGfmpkYp@gmail.com> (raw)
In-Reply-To: <4f3857029d855ed4e513ae01a2e8f018@tipi-net.de>

Hello Nicolai,

On Mon, Aug 24, 2026 at 05:13:13PM +0200, Nicolai Buchwitz wrote:
> On 24.8.2026 13:45, Breno Leitao wrote:
> > While debugging another issue today, I found out that my TX queue is
> > stopped for 136.07 years (4294907392 ms).
> 
> nit: 4294907392 ms is ~49.7 days

Lol, let me fix update it.

> >     bnxt_en 0002:01:00.0 eth0: NETDEV WATCHDOG: CPU: 28: transmit queue
> > 23 timed out 4294907392 ms
> > 
> > 4294907392 is not an elapsed time. It is the value of jiffies at that
> > moment: INITIAL_JIFFIES is 4294667296.
> > 
> > dev_activate() runs transition_one_qdisc() over every TX queue, which
> > resets trans_start to 0, and then stamps only queue 0 through
> > netif_trans_update().
> > 
> > Stamp jiffies instead. A queue stopped across dev_activate() now gets a
> > full watchdog_timeo of grace, and is still reported if it is stopped
> > that long.
> > 
> > Fixes: 9b36627acecd ("net: remove dev->trans_start")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Breno Leitao <leitao@debian.org>
> > ---
> >  net/sched/sch_generic.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
> > index ef2b4bf515641..4539dc2c6d380 100644
> > --- a/net/sched/sch_generic.c
> > +++ b/net/sched/sch_generic.c
> > @@ -1278,7 +1278,7 @@ static void transition_one_qdisc(struct net_device
> > *dev,
> > 
> >  	rcu_assign_pointer(dev_queue->qdisc, new_qdisc);
> >  	if (need_watchdog_p) {
> > -		WRITE_ONCE(dev_queue->trans_start, 0);
> > +		WRITE_ONCE(dev_queue->trans_start, jiffies);
> >  		*need_watchdog_p = 1;
> >  	}
> >  }
> 
> Follow up or v2: netif_trans_update() in dev_activate() now seems redundant?

Yea, good point, we can get rid of netif_trans_update(), given we have
updated all the trans_start in here.

I will respin this one.

Thanks for the review,
--breno

--
pw-bot: cr

      parent reply	other threads:[~2026-08-25 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 11:45 [PATCH net] net: fix spurious TX timeout after dev_activate() Breno Leitao
2026-08-24 15:13 ` Nicolai Buchwitz
2026-08-25  8:47   ` Paolo Abeni
2026-08-25 10:43     ` Breno Leitao
2026-08-25 10:36   ` Breno Leitao [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=ao1bBrMlSGfmpkYp@gmail.com \
    --to=leitao@debian.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nb@tipi-net.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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