From: patchwork-bot+netdevbpf@kernel.org
To: Yao Sang <sangyao@kylinos.cn>
Cc: tariqt@nvidia.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, edumazet@google.com,
gustavoars@kernel.org, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net v2] net/mlx4: avoid GCC 10 __bad_copy_from() false positive
Date: Tue, 09 Jun 2026 00:30:09 +0000 [thread overview]
Message-ID: <178096500989.1726280.2088342671692076500.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260603061044.2055155-1-sangyao@kylinos.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 3 Jun 2026 14:10:44 +0800 you wrote:
> mlx4_init_user_cqes() fills a scratch buffer with the CQE
> initialization pattern and then copies from that buffer to userspace.
>
> In the single-copy path, the copy length is array_size(entries,
> cqe_size), but the scratch buffer is allocated with PAGE_SIZE. GCC 10
> does not carry the branch invariant strongly enough through the object
> size checks and falsely triggers __bad_copy_from().
>
> [...]
Here is the summary with links:
- [net,v2] net/mlx4: avoid GCC 10 __bad_copy_from() false positive
https://git.kernel.org/netdev/net/c/2365343f4aad
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-06-09 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 6:10 [PATCH net v2] net/mlx4: avoid GCC 10 __bad_copy_from() false positive Yao Sang
2026-06-04 19:21 ` Jacob Keller
2026-06-09 0:30 ` 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=178096500989.1726280.2088342671692076500.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sangyao@kylinos.cn \
--cc=tariqt@nvidia.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