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 for Android: free password hash cracker in your pocket

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

Message-ID: <e1384459-4923-4e02-9051-404c5291da95@blackwall.org>
Date: Sun, 22 Dec 2024 11:45:07 +0200
From: Nikolay Aleksandrov <razor@...ckwall.org>
To: Radu Rendec <rrendec@...hat.com>, Ido Schimmel <idosch@...sch.org>,
 Roopa Prabhu <roopa@...dia.com>
Cc: 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 12/19/24 18:36, 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>
> ---
>  drivers/net/vxlan/vxlan_core.c | 4 ++--
>  drivers/net/vxlan/vxlan_mdb.c  | 2 +-
>  include/net/dropreason-core.h  | 6 +++---
>  3 files changed, 6 insertions(+), 6 deletions(-)
> 

Acked-by: Nikolay Aleksandrov <razor@...ckwall.org>