From: patchwork-bot+netdevbpf@kernel.org
To: Tim Douglas <me@timdoug.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: lib8390: avoid truncating the expected receive page
Date: Sat, 21 Nov 2026 21:10:05 +0000 [thread overview]
Message-ID: <179529540503.1173579.951432100954985281.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118022217.84500-1-me@timdoug.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Nov 2026 21:22:17 -0500 you wrote:
> For a receive ring ending at page 0xff, the expected next page can
> exceed 0xff before the ring size is subtracted. The value is
> truncated when stored in an unsigned char, so a valid frame that
> wraps around the ring can be rejected and queued frames dropped.
> Store the intermediate value in an int.
>
> This was observed with the 64 KiB receive ring enabled on a
> Farallon EtherMac LC-TP. With the fix, three 16 MiB downloads on a
> Performa 6200CD using a kernel with local platform support completed
> without receive errors. The pcnet_cs driver also uses a receive ring
> ending at page 0xff for Socket EA cards with the large buffer enabled.
>
> [...]
Here is the summary with links:
- [net] net: lib8390: avoid truncating the expected receive page
https://git.kernel.org/netdev/net-next/c/720a6f58c0ba
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-11-21 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 2:22 [PATCH net] net: lib8390: avoid truncating the expected receive page Tim Douglas
2026-11-19 11:48 ` Daniel Machon
2026-11-21 21:10 ` 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=179529540503.1173579.951432100954985281.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@timdoug.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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