From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH net-next v4 0/4] net: selftest: improve test string formatting and checksum handling
Date: Wed, 25 Jun 2025 13:21:17 -0700 [thread overview]
Message-ID: <20250625132117.1b3264e8@kernel.org> (raw)
In-Reply-To: <aFuEHpbjGILWich1@pengutronix.de>
On Wed, 25 Jun 2025 07:07:42 +0200 Oleksij Rempel wrote:
> Hm... at least part of this behavior can be verified with self-tests:
>
> - Send a TCP packet with an intentionally incorrect checksum,
> ensuring its state is CHECKSUM_NONE so the transmit path doesn't change it.
> - Test if we receive this packet back via the PHY loopback.
> - If received: The test checks the ip_summed status of the
> received packet.
> - A status of CHECKSUM_NONE indicates the hardware correctly passed
> the packet up without validating it.
_NONE or _COMPLETE are both fine in this case.
> - A status of CHECKSUM_UNNECESSARY indicates a failure, as the hardware
> or driver incorrectly marked a bad checksum as good.
> - If not received (after a timeout): The test then checks the device's
> error statistics.
> - If the rx_errors counter has incremented
> - If the counter has not incremented, the packet was lost for an unknown
> reason, and the test fails.
>
> What do you think?
Sounds like a good idea! Not sure if I'd bother with the rx_error
handling. Hopefully the drivers can be configured to pass the packet
thru.
next prev parent reply other threads:[~2025-06-25 20:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 8:30 [PATCH net-next v4 0/4] net: selftest: improve test string formatting and checksum handling Oleksij Rempel
2025-05-15 8:30 ` [PATCH net-next v4 1/4] net: selftests: drop test index from net_selftest_get_strings() Oleksij Rempel
2025-05-15 8:30 ` [PATCH net-next v4 2/4] net: selftests: prepare for detailed error handling in net_test_get_skb() Oleksij Rempel
2025-05-15 8:30 ` [PATCH net-next v4 3/4] net: selftests: add checksum mode support and SW checksum handling Oleksij Rempel
2025-05-16 12:57 ` Simon Horman
2025-05-17 1:48 ` Jakub Kicinski
2025-05-15 8:31 ` [PATCH net-next v4 4/4] net: selftests: add PHY loopback tests with HW checksum offload Oleksij Rempel
2025-05-17 1:45 ` [PATCH net-next v4 0/4] net: selftest: improve test string formatting and checksum handling Jakub Kicinski
2025-06-20 10:53 ` Oleksij Rempel
2025-06-21 13:46 ` Jakub Kicinski
2025-06-23 11:45 ` Oleksij Rempel
2025-06-23 17:19 ` Jakub Kicinski
2025-06-24 8:26 ` Oleksij Rempel
2025-06-24 16:09 ` Jakub Kicinski
2025-06-25 5:07 ` Oleksij Rempel
2025-06-25 20:21 ` Jakub Kicinski [this message]
2025-07-11 8:42 ` Marc Kleine-Budde
2025-07-11 22:36 ` Jakub Kicinski
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=20250625132117.1b3264e8@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).