All of lore.kernel.org
 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 2/8] psp: don't encapsulate ipv6 packets with extension headers
Date: Thu, 12 Nov 2026 00:30:59 +0000	[thread overview]
Message-ID: <sashiko-outbox-209926@kernel.org> (raw)
In-Reply-To: <20261111001831.3710881-3-toddfreed@meta.com>

> psp_dev_encapsulate() inserts the udp+psp headers at the transport
> header, rewrites the protocol of the fixed ip header to udp, and writes
> tcp as the psp next header. so tcp must directly follow the fixed
> header.
> 
> if the packet is an ipv6 packet with extension headers, udp+psp is
> placed after them, but the next header indicating the l4 protocol is on
> the last extension header in the chain, not in the fixed header.
> therefore this produces a malformed packet.
> 
> in addition to being malformed, with mlx5 this kind of packet goes out
> unencrypted. since the tx association encodes intent to send encrypted
> packets, drop such packets instead.
> 
> a psp tcp socket emits such packets if certain socket options are set on
> it (e.g. IPV6_DSTOPTS). refusing the combination of such socket options
> with psp association would be helpful but is not implemented here. since
> extension headers can also come from a route the datapath check is
> needed anyway.
> 
> the check also covers ipv4: the l4 protocol must be tcp, and the
> transport header must follow the ip header and its options. packets of
> a psp tcp socket always pass it.
> 
> Fixes: fc724515741a ("psp: provide encapsulation helper for drivers")
> Signed-off-by: Todd Freed <toddfreed@meta.com>

Sashiko has reviewed this patch and found no issues.

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


  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 [this message]
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
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-209926@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.