mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: fredrik.nyberg@volvocars.com
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jose Alonso <joalonsof@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH net] net: usb: ax88179_178a: fix rx frame length for non-last packets
Date: Wed, 7 Oct 2026 15:31:37 +0100	[thread overview]
Message-ID: <20261007143137.GQ83879@horms.kernel.org> (raw)
In-Reply-To: <20261002-ax88179-rx-len-v1-1-f01a2a295079@volvocars.com>

On Fri, Oct 02, 2026 at 02:28:57PM +0200, Fredrik Nyberg via B4 Relay wrote:
> From: Fredrik Nyberg <fredrik.nyberg@volvocars.com>
> 
> Commit 4ce62d5b2f7a ("net: usb: ax88179_178a: stop lying about
> skb->truesize") replaced skb_clone() with a copy into a new skb for
> every packet of a bulk-in transfer except the last one. The copy skips
> the 2-byte IP alignment pseudo header but still copies pkt_len bytes,
> and pkt_len includes that header. Each of these frames is therefore
> delivered with two extra trailing bytes: the 0xeeee pseudo header of
> the next slot when the frame ends on an 8-byte boundary, or slot
> padding otherwise. The last packet is still trimmed to pkt_len - 2.
> 
> IPv4 and IPv6 trim the extra bytes, so most traffic is unaffected.
> Anything that relies on the frame length is not. MACsec takes the ICV
> from the last 16 bytes and drops every such frame as InPktsNotValid. In
> our setup that was 0.2-1.2% of received MACsec frames, depending on how
> many frames shared a transfer, including service discovery multicast.
> 
> Allocate and copy pkt_len - 2 bytes, like the last-packet path.
> 
> Fixes: 4ce62d5b2f7a ("net: usb: ax88179_178a: stop lying about skb->truesize")
> Cc: stable@vger.kernel.org
> Signed-off-by: Fredrik Nyberg <fredrik.nyberg@volvocars.com>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2026-10-07 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 12:28 Fredrik Nyberg via B4 Relay
2026-10-07 14:31 ` Simon Horman [this message]
2026-10-07 23:44 ` Jakub Kicinski
2026-10-07 23:50 ` 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=20261007143137.GQ83879@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=fredrik.nyberg@volvocars.com \
    --cc=joalonsof@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@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®