netdev - Re: [PATCH v3 net-next] udp_tunnel: use netdev_warn() instead of netdev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <175764480970.2382321.18187125356507305675.git-patchwork-notify@kernel.org>
Date: Fri, 12 Sep 2025 02:40:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: ALOK TIWARI <alok.a.tiwari@...cle.com>
Cc: dsahern@...nel.org, davem@...emloft.net, edumazet@...gle.com,
 kuba@...nel.org, pabeni@...hat.com, horms@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next] udp_tunnel: use netdev_warn() instead of
 netdev_WARN()

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:

On Wed, 10 Sep 2025 12:50:26 -0700 you wrote:
> netdev_WARN() uses WARN/WARN_ON to print a backtrace along with
> file and line information. In this case, udp_tunnel_nic_register()
> returning an error is just a failed operation, not a kernel bug.
> 
> udp_tunnel_nic_register() can fail in two ways:
> 1. "-EINVAL":
> Invalid or inconsistent udp_tunnel_nic_info provided by the driver
> (e.g. set_port without a matching unset_port, missing sync_table,
> first table with zero entries). These paths already trigger an
> internal WARN_ON(), so misuse is caught and logged with a backtrace.
> 
> [...]

Here is the summary with links:
  - [v3,net-next] udp_tunnel: use netdev_warn() instead of netdev_WARN()
    https://git.kernel.org/netdev/net-next/c/dc2f650f7e68

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