From: patchwork-bot+netdevbpf@kernel.org
To: Pei Xiao <xiaopei01@kylinos.cn>
Cc: lkp@intel.com, alexanderduyck@fb.com, kernel-team@meta.com,
netdev@vger.kernel.org, horms@kernel.org, kuba@kernel.org,
lee@trager.us, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev, pabeni@redhat.com
Subject: Re: [PATCH] eth: fbnic: fix integer overflow warning in TLV_MAX_DATA definition
Date: Thu, 23 Oct 2025 03:46:16 +0000 [thread overview]
Message-ID: <176119117676.2145463.10144749814100093339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <182b9d0235d044d69d7a57c1296cc6f46e395beb.1761039651.git.xiaopei01@kylinos.cn>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 21 Oct 2025 17:42:27 +0800 you wrote:
> The TLV_MAX_DATA macro calculates (PAGE_SIZE - 512) which can exceed
> the maximum value of a 16-bit unsigned integer on architectures with
> large page sizes, causing compiler warnings:
>
> drivers/net/ethernet/meta/fbnic/fbnic_tlv.h:83:24: warning: conversion
> from 'long unsigned int' to 'short unsigned int' changes value from
> '261632' to '65024' [-Woverflow]
>
> [...]
Here is the summary with links:
- eth: fbnic: fix integer overflow warning in TLV_MAX_DATA definition
https://git.kernel.org/netdev/net-next/c/d550d63d0082
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:[~2025-10-23 3:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 0:17 drivers/net/ethernet/meta/fbnic/fbnic_tlv.h:83:24: warning: conversion from 'long unsigned int' to 'u16' {aka 'short unsigned int'} changes value from '261632' to '65024' kernel test robot
2025-10-21 9:42 ` [PATCH] eth: fbnic: fix integer overflow warning in TLV_MAX_DATA definition Pei Xiao
2025-10-23 3:46 ` 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=176119117676.2145463.10144749814100093339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=xiaopei01@kylinos.cn \
/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