From: patchwork-bot+netdevbpf@kernel.org
To: Pengpeng Hou <hppiscas@163.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
enelsonmoore@gmail.com, peter@korsgaard.com, horms@kernel.org,
andrew@lunn.ch
Subject: Re: [PATCH net v2] net: usb: sr9700: include receive overhead in the length check
Date: Tue, 22 Sep 2026 00:30:06 +0000 [thread overview]
Message-ID: <179003700639.3305732.13568325130499669966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260920034745.18468-1-hppiscas@163.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 20 Sep 2026 11:47:45 +0800 you wrote:
> The receive fixup subtracts the Ethernet CRC from the reported packet
> length, but compares that payload length against the whole remaining
> receive buffer. The following copy starts after the three-byte header,
> and the cursor advance consumes both that header and the four-byte CRC.
>
> Require the payload to fit after SR_RX_OVERHEAD before copying it or
> advancing to the next packet. The loop already ensures that the
> remaining buffer is larger than the overhead, so the subtraction is
> safe.
>
> [...]
Here is the summary with links:
- [net,v2] net: usb: sr9700: include receive overhead in the length check
https://git.kernel.org/netdev/net/c/c06bde80ae7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-22 0:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 3:47 [PATCH net v2] net: usb: sr9700: include receive overhead in the length check Pengpeng Hou
2026-09-22 0:30 ` patchwork-bot+netdevbpf [this message]
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=179003700639.3305732.13568325130499669966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=horms@kernel.org \
--cc=hppiscas@163.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=peter@korsgaard.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