From: patchwork-bot+netdevbpf@kernel.org
To: Tyllis Xu <livelycarpet87@gmail.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, peppe.cavallaro@st.com,
rayagond@vayavyalabs.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, danisjiang@gmail.com,
ychen@northwestern.edu, LivelyCarpet87@gmail.com
Subject: Re: [PATCH net v2] net: stmmac: fix integer underflow in chain mode
Date: Fri, 03 Apr 2026 01:40:05 +0000 [thread overview]
Message-ID: <177518040504.695500.16991408792529734649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260401044708.1386919-1-LivelyCarpet87@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 31 Mar 2026 23:47:07 -0500 you wrote:
> The jumbo_frm() chain-mode implementation unconditionally computes
>
> len = nopaged_len - bmax;
>
> where nopaged_len = skb_headlen(skb) (linear bytes only) and bmax is
> BUF_SIZE_8KiB or BUF_SIZE_2KiB. However, the caller stmmac_xmit()
> decides to invoke jumbo_frm() based on skb->len (total length including
> page fragments):
>
> [...]
Here is the summary with links:
- [net,v2] net: stmmac: fix integer underflow in chain mode
https://git.kernel.org/netdev/net/c/51f4e090b9f8
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-04-03 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 4:10 [PATCH] net: stmmac: fix integer underflow in chain mode jumbo_frm Tyllis Xu
2026-03-23 14:18 ` Simon Horman
2026-03-24 6:07 ` Tyllis Xu
2026-03-25 17:09 ` Russell King (Oracle)
2026-04-01 4:47 ` [PATCH net v2] net: stmmac: fix integer underflow in chain mode Tyllis Xu
2026-04-03 1:40 ` 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=177518040504.695500.16991408792529734649.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=danisjiang@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=livelycarpet87@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=rayagond@vayavyalabs.com \
--cc=stable@vger.kernel.org \
--cc=ychen@northwestern.edu \
/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