mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	linux-can@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v1 0/2] fix statistics for CAN RTR and Error frames
Date: Tue, 23 Nov 2021 22:10:08 +0100	[thread overview]
Message-ID: <bc682dbe-c74e-cd8a-ab05-78a6b4079ebf@hartkopp.net> (raw)
In-Reply-To: <20211123115333.624335-1-mailhol.vincent@wanadoo.fr>



On 23.11.21 12:53, Vincent Mailhol wrote:
> There are two common errors which are made when reporting the CAN RX
> statistics:
> 
>    1. Incrementing the "normal" RX stats when receiving an Error
>    frame. Error frames is an abstraction of Socket CAN and does not
>    exist on the wire.
> 
>    2. Counting the length of the Remote Transmission Frames (RTR). The
>    length of an RTR frame is the length of the requested frame not the
>    actual payload. In reality the payload of an RTR frame is always 0
>    bytes long.
> 
> This patch series fix those two issues for all CAN drivers.
> 
> Vincent Mailhol (2):
>    can: do not increase rx statistics when receiving CAN error frames
>    can: do not increase rx_bytes statistics for RTR frames

I would suggest to upstream this change without bringing it to older 
(stable) trees.

It doesn't fix any substantial flaw which needs to be backported IMHO.

Btw. can you please change 'error frames' to 'error message frames'?

We had a discussion some years ago that the 'error frames' are used as 
term inside the CAN protocol.

Thanks,
Oliver


> 
>   drivers/net/can/at91_can.c                      |  9 ++-------
>   drivers/net/can/c_can/c_can_main.c              |  8 ++------
>   drivers/net/can/cc770/cc770.c                   |  6 ++----
>   drivers/net/can/dev/dev.c                       |  4 ----
>   drivers/net/can/dev/rx-offload.c                |  7 +++++--
>   drivers/net/can/grcan.c                         |  3 ++-
>   drivers/net/can/ifi_canfd/ifi_canfd.c           |  8 ++------
>   drivers/net/can/janz-ican3.c                    |  3 ++-
>   drivers/net/can/kvaser_pciefd.c                 |  8 ++------
>   drivers/net/can/m_can/m_can.c                   | 10 ++--------
>   drivers/net/can/mscan/mscan.c                   | 10 ++++++----
>   drivers/net/can/pch_can.c                       |  6 ++----
>   drivers/net/can/peak_canfd/peak_canfd.c         |  7 ++-----
>   drivers/net/can/rcar/rcar_can.c                 |  9 +++------
>   drivers/net/can/rcar/rcar_canfd.c               |  7 ++-----
>   drivers/net/can/sja1000/sja1000.c               |  5 ++---
>   drivers/net/can/slcan.c                         |  3 ++-
>   drivers/net/can/spi/hi311x.c                    |  3 ++-
>   drivers/net/can/spi/mcp251x.c                   |  3 ++-
>   drivers/net/can/sun4i_can.c                     | 10 ++++------
>   drivers/net/can/usb/ems_usb.c                   |  5 ++---
>   drivers/net/can/usb/esd_usb2.c                  |  5 ++---
>   drivers/net/can/usb/etas_es58x/es58x_core.c     |  7 -------
>   .../net/can/usb/kvaser_usb/kvaser_usb_core.c    |  2 --
>   .../net/can/usb/kvaser_usb/kvaser_usb_hydra.c   | 14 ++++----------
>   .../net/can/usb/kvaser_usb/kvaser_usb_leaf.c    |  7 ++-----
>   drivers/net/can/usb/mcba_usb.c                  |  3 ++-
>   drivers/net/can/usb/peak_usb/pcan_usb.c         |  5 ++---
>   drivers/net/can/usb/peak_usb/pcan_usb_fd.c      | 11 ++++-------
>   drivers/net/can/usb/peak_usb/pcan_usb_pro.c     | 11 +++++------
>   drivers/net/can/usb/ucan.c                      |  7 +++++--
>   drivers/net/can/usb/usb_8dev.c                  | 10 ++++------
>   drivers/net/can/xilinx_can.c                    | 17 ++++++-----------
>   33 files changed, 86 insertions(+), 147 deletions(-)
> 

  parent reply	other threads:[~2021-11-23 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 11:53 Vincent Mailhol
2021-11-23 11:53 ` [PATCH v1 1/2] can: do not increase rx statistics when receiving CAN error frames Vincent Mailhol
2021-11-23 21:01   ` Oliver Hartkopp
2021-11-23 23:21     ` Vincent MAILHOL
2021-11-23 11:53 ` [PATCH v1 2/2] can: do not increase rx_bytes statistics for RTR frames Vincent Mailhol
2021-11-23 18:10   ` Vincent MAILHOL
2021-11-24 17:59   ` Stefan Mätje
2021-11-24 23:55     ` Vincent MAILHOL
2021-11-23 21:10 ` Oliver Hartkopp [this message]
2021-11-23 23:35   ` [PATCH v1 0/2] fix statistics for CAN RTR and Error frames Vincent MAILHOL

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=bc682dbe-c74e-cd8a-ab05-78a6b4079ebf@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=mkl@pengutronix.de \
    --cc=netdev@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

all inboxes | Powered by JetHome®