[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176065500875.1934842.18128333206683438556.git-patchwork-notify@kernel.org>
Date: Thu, 16 Oct 2025 22:50:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Nathan Chancellor <nathan@...nel.org>
Cc: saeedm@...dia.com, leon@...nel.org, tariqt@...dia.com, mbloch@...dia.com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, nick.desaulniers+lkml@...il.com,
morbo@...gle.com, justinstitt@...gle.com, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, patches@...ts.linux.dev, llvm@...ts.linux.dev
Subject: Re: [PATCH net] net/mlx5e: Return 1 instead of 0 in invalid case in
mlx5e_mpwrq_umr_entry_size()
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 14 Oct 2025 13:46:49 -0700 you wrote:
> When building with Clang 20 or newer, there are some objtool warnings
> from unexpected fallthroughs to other functions:
>
> vmlinux.o: warning: objtool: mlx5e_mpwrq_mtts_per_wqe() falls through to next function mlx5e_mpwrq_max_num_entries()
> vmlinux.o: warning: objtool: mlx5e_mpwrq_max_log_rq_size() falls through to next function mlx5e_get_linear_rq_headroom()
>
> LLVM 20 contains an (admittedly problematic [1]) optimization [2] to
> convert divide by zero into the equivalent of __builtin_unreachable(),
> which invokes undefined behavior and destroys code generation when it is
> encountered in a control flow graph.
>
> [...]
Here is the summary with links:
- [net] net/mlx5e: Return 1 instead of 0 in invalid case in mlx5e_mpwrq_umr_entry_size()
https://git.kernel.org/netdev/net/c/aaf043a56881
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists