From: patchwork-bot+netdevbpf@kernel.org
To: Nate Karstens <nate.karstens@garmin.com>
Cc: netdev@vger.kernel.org, nate.karstens@gmail.com,
tom@quantonium.net, sd@queasysnail.net, jacob.e.keller@intel.com,
stable@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
martin.lau@kernel.org, jakub@cloudflare.com, mrpre@163.com,
linux@treblig.org, tom@herbertland.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] strparser: Fix signed/unsigned mismatch bug
Date: Sat, 08 Nov 2025 02:30:06 +0000 [thread overview]
Message-ID: <176256900601.1226704.4652843459879323361.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251106222835.1871628-1-nate.karstens@garmin.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Nov 2025 16:28:33 -0600 you wrote:
> The `len` member of the sk_buff is an unsigned int. This is cast to
> `ssize_t` (a signed type) for the first sk_buff in the comparison,
> but not the second sk_buff. On 32-bit systems, this can result in
> an integer underflow for certain values because unsigned arithmetic
> is being used.
>
> This appears to be an oversight: if the intention was to use unsigned
> arithmetic, then the first cast would have been omitted. The change
> ensures both len values are cast to `ssize_t`.
>
> [...]
Here is the summary with links:
- [net,v2] strparser: Fix signed/unsigned mismatch bug
https://git.kernel.org/netdev/net/c/4da4e4bde1c4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-11-08 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 22:28 Nate Karstens
2025-11-07 9:56 ` Jacob Keller
2025-11-07 15:01 ` Sabrina Dubroca
2025-11-08 2:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-06 16:36 [PATCH] " Nate Karstens
2025-11-06 16:51 ` [PATCH net v2] " Nate Karstens
2025-11-06 22:22 ` Jakub Kicinski
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=176256900601.1226704.4652843459879323361.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jakub@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=martin.lau@kernel.org \
--cc=mrpre@163.com \
--cc=nate.karstens@garmin.com \
--cc=nate.karstens@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=stable@vger.kernel.org \
--cc=tom@herbertland.com \
--cc=tom@quantonium.net \
/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®