netdev - Re: [PATCH net-next v3 1/2] net: vxlan: rename SKB_DROP_REASON_VXLAN_NO

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z2fKHbXg0TLYD4k7@shredder>
Date: Sun, 22 Dec 2024 10:13:17 +0200
From: Ido Schimmel <idosch@...sch.org>
To: Radu Rendec <rrendec@...hat.com>
Cc: Nikolay Aleksandrov <razor@...ckwall.org>,
	Roopa Prabhu <roopa@...dia.com>, bridge@...ts.linux.dev,
	netdev@...r.kernel.org, Simon Horman <horms@...nel.org>,
	Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
	Eric Dumazet <edumazet@...gle.com>,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next v3 1/2] net: vxlan: rename
 SKB_DROP_REASON_VXLAN_NO_REMOTE

On Thu, Dec 19, 2024 at 11:36:05AM -0500, Radu Rendec wrote:
> The SKB_DROP_REASON_VXLAN_NO_REMOTE skb drop reason was introduced in
> the specific context of vxlan. As it turns out, there are similar cases
> when a packet needs to be dropped in other parts of the network stack,
> such as the bridge module.
> 
> Rename SKB_DROP_REASON_VXLAN_NO_REMOTE and give it a more generic name,
> so that it can be used in other parts of the network stack. This is not
> a functional change, and the numeric value of the drop reason even
> remains unchanged.
> 
> Signed-off-by: Radu Rendec <rrendec@...hat.com>

Reviewed-by: Ido Schimmel <idosch@...dia.com>