All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, mengyuanlou@net-swift.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, jacob.e.keller@intel.com,
	horms@kernel.org, aleksandr.loktionov@intel.com,
	fabio.baltieri@gmail.com, larysa.zaremba@intel.com
Subject: Re: [PATCH net] net: wangxun: use BIT_ULL() to prevent shift overflow on 32-bit archs
Date: Thu, 27 Aug 2026 10:20:07 +0000	[thread overview]
Message-ID: <178782600740.1149245.16577803441749400206.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <45F5565CE6AC4329+20260824072119.48399-1-jiawenwu@trustnetic.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 24 Aug 2026 15:21:19 +0800 you wrote:
> The macros TXGBE_INTR_MISC() and WX_INTR_Q() rely on the standard BIT()
> macro to generate interrupt masks based on the queue vector index.
> 
> On 32-bit architectures, BIT() evaluates to a 32-bit `unsigned long`.
> Since the number of queue vectors can be up to 63 on txgbe devices,
> performing a left shift of 32 or more results in an integer overflow
> and undefined behavior. This causes incorrect interrupt masking and
> unmasking logic for both the queue and miscellaneous interrupts on
> 32-bit systems.
> 
> [...]

Here is the summary with links:
  - [net] net: wangxun: use BIT_ULL() to prevent shift overflow on 32-bit archs
    https://git.kernel.org/netdev/net/c/63c885688f38

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-27 10:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24  7:21 [PATCH net] net: wangxun: use BIT_ULL() to prevent shift overflow on 32-bit archs Jiawen Wu
2026-08-24  8:35 ` Loktionov, Aleksandr
2026-08-27 10:20 ` 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=178782600740.1149245.16577803441749400206.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fabio.baltieri@gmail.com \
    --cc=horms@kernel.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=kuba@kernel.org \
    --cc=larysa.zaremba@intel.com \
    --cc=mengyuanlou@net-swift.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.