Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Nicolai Buchwitz <nb@tipi-net.de>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>
Cc: netdev-bot+sashiko@kernel.org, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, o.rempel@pengutronix.de, andrew+netdev@lunn.ch,
	mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
	Jose.Abreu@synopsys.com, saeedm@nvidia.com, tariqt@nvidia.com,
	mbloch@nvidia.com, leon@kernel.org, dtatulea@nvidia.com,
	alazar@nvidia.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] net: selftests: use skb_share_check() in the loopback receive hook
Date: Thu, 15 Oct 2026 10:01:41 +0200	[thread overview]
Message-ID: <d28efab10f43a46d51cdfd978b0a1e90@tipi-net.de> (raw)
In-Reply-To: <cccfd292-6169-449e-a675-a9bb54ec4191@bootlin.com>

Hi Maxime

On 15.10.2026 09:46, Maxime Chevallier wrote:

> [...]

>>> Could an IPv4 frame that arrives during ethtool -t make the hook read 
>>> up
>>> to about 64 bytes past skb->tail? Examples would be a minimum-size 
>>> TCP
>>> segment or a frame with ihl=15.
>>> 
>>> The over-read seems to stay inside the skb head allocation, because
>>> skb_shared_info follows skb->end. If so, the only effect is a 
>>> possibly
>>> wrong selftest result.
>> 
>> The length check is pre-existing, will address that in a follow-up 
>> patch.
> 
> I'm unsure about this, Can we instead assume that when one is running 
> the
> "ethtool -t" selftests on a machine, they are doing so in some 
> controlled
> conditions ?
> 
> IOW can we take the assumption that we won't get incoming traffic at 
> the same
> time as we run the selftests, and if we do get some and that triggers a 
> wrong
> result, this is expected ? ethtool selftests are very cheap to run, 
> only a
> handful of seconds, and don't require any extra dependency, it doesn't 
> cost
> much to re-run them if something unexpected happens during them.
> 
> ofc. getting a stray frame during the selftests mustn't crash :)
> 
> That's my take on these tests, but feel free to disagree :)

Also fine with me. A stray frame just fails the magic check and gets
dropped anyway, so the test result doesn't even change...

Two patches less to fight with Clashiko over :)

Regards
Nicolai

  reply	other threads:[~2026-10-15  8:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 18:29 [PATCH net-next 0/3] net: use skb_share_check() in loopback selftest hooks Nicolai Buchwitz
2026-10-07 18:29 ` [PATCH net-next 1/3] net: selftests: use skb_share_check() in the loopback receive hook Nicolai Buchwitz
2026-10-07 18:43   ` sashiko-bot
2026-10-08 21:31   ` netdev-bot+sashiko
2026-10-09  6:49     ` Nicolai Buchwitz
2026-10-15  7:46       ` Maxime Chevallier
2026-10-15  8:01         ` Nicolai Buchwitz [this message]
2026-10-09 16:59   ` Simon Horman
2026-10-07 18:29 ` [PATCH net-next 2/3] net: stmmac: " Nicolai Buchwitz
2026-10-07 18:43   ` sashiko-bot
2026-10-09 16:59   ` Simon Horman
2026-10-07 18:29 ` [PATCH net-next 3/3] net/mlx5e: use skb_share_check() in the loopback selftest hook Nicolai Buchwitz
2026-10-07 18:43   ` sashiko-bot
2026-10-08 21:31   ` netdev-bot+sashiko
2026-10-09  8:37     ` Nicolai Buchwitz
2026-10-09 17:00   ` Simon Horman
2026-10-12 19:07   ` Tariq Toukan
2026-10-14 20:06 ` [PATCH net-next 0/3] net: use skb_share_check() in loopback selftest hooks Jakub Kicinski
2026-10-14 21:02   ` Nicolai Buchwitz
2026-10-14 21:40 ` patchwork-bot+netdevbpf

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=d28efab10f43a46d51cdfd978b0a1e90@tipi-net.de \
    --to=nb@tipi-net.de \
    --cc=Jose.Abreu@synopsys.com \
    --cc=alazar@nvidia.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mbloch@nvidia.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.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