Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Todd Freed" <toddfreed@meta.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net v5 7/8] selftests: drv-net: psp: test that ipv4 psp packets aren't fragmented
Date: Thu, 12 Nov 2026 00:31:02 +0000	[thread overview]
Message-ID: <sashiko-outbox-209931@kernel.org> (raw)
In-Reply-To: <20261111001831.3710881-8-toddfreed@meta.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] selftests: drv-net: psp: open-coded ctl_file_write() in
  data_send_ipv4_frags()
--

commit f2ab5974348f0d91190d725cd849415716fc0e2e
Author: Todd Freed <toddfreed@meta.com>

selftests: drv-net: psp: test that ipv4 psp packets aren't fragmented

This commit adds a selftest verifying that IPv4 TCP packets on a PSP
socket that exceed the device MTU are dropped rather than fragmented and
sent unencrypted.

> diff --git a/tools/testing/selftests/drivers/net/psp.py b/tools/testing/selftests/drivers/net/psp.py
> index 7e251439a2fd9..5dac62ad96b0b 100755
> --- a/tools/testing/selftests/drivers/net/psp.py
> +++ b/tools/testing/selftests/drivers/net/psp.py

[ ... ]

> @@ -799,6 +801,105 @@ def data_send_ipv6_exthdr(cfg, opt, val):

[ ... ]

> +def data_send_ipv4_frags(cfg):

[ ... ]

> +    # With MTU probing on, TCP caps the MSS at the probing base, whatever
> +    # the route MTU
> +    probing_path = "/proc/sys/net/ipv4/tcp_mtu_probing"
> +    with open(probing_path, encoding="utf-8") as fp:
> +        probing = fp.read().strip()
> +    if int(probing) > 1:
> +        def set_probing(val):
> +            with open(probing_path, "w", encoding="utf-8") as fp:
> +                fp.write(val)
> +        set_probing("0")
> +        defer(set_probing, probing)

[Severity: Low]
Could this use ctl_file_write("/proc/sys/net/ipv4/tcp_mtu_probing", 0)
from lib.py instead of open-coding the read, write, and deferred restore?

Also, only clearing tcp_mtu_probing when it is greater than 1 leaves blackhole
detection (1) enabled, which can still enable MTU probing and lower the socket
MSS during the 3-second s.sendall() timeout window if retransmissions pass
tcp_retries1.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111001831.3710881-1-toddfreed@meta.com?part=7

  reply	other threads:[~2026-11-12  0:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  0:18 [PATCH net v5 0/8] psp, tls: don't send offloaded contents in cleartext Todd Freed
2026-11-11  0:18 ` [PATCH net v5 1/8] net/mlx5e: ring the tx doorbell when an accel offload drops a packet Todd Freed
2026-11-12  0:30   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 2/8] psp: don't encapsulate ipv6 packets with extension headers Todd Freed
2026-11-12  0:30   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 3/8] net: don't fragment decrypted skbs Todd Freed
2026-11-12  0:31   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 4/8] ipv4: icmp: don't quote decrypted payload in icmp errors Todd Freed
2026-11-12  0:31   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 5/8] ipv6: icmpv6: don't quote decrypted payload in icmpv6 errors Todd Freed
2026-11-12  0:31   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 6/8] selftests: drv-net: psp: test ipv6 tcp socket with extension headers Todd Freed
2026-11-12  0:31   ` sashiko-bot
2026-11-11  0:18 ` [PATCH net v5 7/8] selftests: drv-net: psp: test that ipv4 psp packets aren't fragmented Todd Freed
2026-11-12  0:31   ` sashiko-bot [this message]
2026-11-11  0:18 ` [PATCH net v5 8/8] net/mlx5e: psp: tso: replace only the length in checksum seed Todd Freed
2026-11-12  0:31   ` sashiko-bot

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=sashiko-outbox-209931@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=toddfreed@meta.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