From: patchwork-bot+netdevbpf@kernel.org
To: Mohsin Bashir <mohsin.bashr@gmail.com>
Cc: netdev@vger.kernel.org, alexanderduyck@fb.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, jacob.e.keller@intel.com, kernel-team@meta.com,
kuba@kernel.org, lee@trager.us, pabeni@redhat.com,
sanman.p211993@gmail.com
Subject: Re: [PATCH net] eth: fbnic: Fix counter roll-over issue
Date: Thu, 27 Nov 2025 03:16:27 +0000 [thread overview]
Message-ID: <176421338749.1916399.7175645336781698371.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251125211704.3222413-1-mohsin.bashr@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Nov 2025 13:17:04 -0800 you wrote:
> Fix a potential counter roll-over issue in fbnic_mbx_alloc_rx_msgs()
> when calculating descriptor slots. The issue occurs when head - tail
> results in a large positive value (unsigned) and the compiler interprets
> head - tail - 1 as a signed value.
>
> Since FBNIC_IPC_MBX_DESC_LEN is a power of two, use a masking operation,
> which is a common way of avoiding this problem when dealing with these
> sort of ring space calculations.
>
> [...]
Here is the summary with links:
- [net] eth: fbnic: Fix counter roll-over issue
https://git.kernel.org/netdev/net/c/6d66e093e074
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-11-27 3:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 21:17 [PATCH net] eth: fbnic: Fix counter roll-over issue Mohsin Bashir
2025-11-27 3:16 ` 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=176421338749.1916399.7175645336781698371.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sanman.p211993@gmail.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;
as well as URLs for NNTP newsgroup(s).