mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: netdev-bot+sashiko@kernel.org
Cc: mmyangfl@gmail.com, netdev@vger.kernel.org, olteanv@gmail.com,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/4] net: dsa: motorcomm: Fix stats64 error counter mapping
Date: Tue, 10 Nov 2026 14:20:59 +0100	[thread overview]
Message-ID: <84b7c0d7-c167-43ab-9384-869c0bb40ea5@lunn.ch> (raw)
In-Reply-To: <179414774671.994134.1756882573318817305@kernel.org>

> [Severity: Medium]
> With the tx_fifo_errors mapping removed, TX undersize events are no
> longer counted in any rtnl_link_stats64 field, and that includes
> tx_errors. Is this intended?
> 
> The tx_errors kernel-doc in include/uapi/linux/if_link.h says:
> 
>  * @tx_errors: Total number of transmit problems.
>  *   This counter must include events counter by @tx_aborted_errors,
>  *   @tx_carrier_errors, @tx_fifo_errors, @tx_heartbeat_errors,
>  *   @tx_window_errors and other errors not otherwise counted.
> 
> A runt frame may not be a FIFO underrun. Could tx_undersize_errors still
> be added to tx_errors as an error not otherwise counted?

It should not be possible to send runt frame, i expect either the
hardware, or the driver to pad them to 64 bytes. So i don't think what
the LLM is saying is valid.

However, it would be good to get this counter reported somewhere.

	 Andrew

  reply	other threads:[~2026-11-10 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 13:20 [PATCH net-next 0/4] net: dsa: motorcomm: MIB fixup David Yang
2026-11-07 13:20 ` [PATCH net-next 1/4] net: dsa: motorcomm: Fix stats64 error counter mapping David Yang
2026-11-08 14:22   ` netdev-bot+sashiko
2026-11-10 13:20     ` Andrew Lunn [this message]
2026-11-07 13:20 ` [PATCH net-next 2/4] net: dsa: motorcomm: Fix RMON fragments stat David Yang
2026-11-08 14:22   ` netdev-bot+sashiko
2026-11-10 13:21   ` Andrew Lunn
2026-11-07 13:20 ` [PATCH net-next 3/4] net: dsa: motorcomm: Use safe 64-bit counter reader David Yang
2026-11-08 14:22   ` netdev-bot+sashiko
2026-11-07 13:20 ` [PATCH net-next 4/4] net: dsa: motorcomm: Prevent rx_bytes/tx_bytes underflow David Yang
2026-11-08 14:22   ` netdev-bot+sashiko

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=84b7c0d7-c167-43ab-9384-869c0bb40ea5@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmyangfl@gmail.com \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@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

all inboxes | Powered by JetHome®