netdev - Re: [PATCH net-next] net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as _

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

Message-Id: <161644440812.26518.17110056440678618651.git-patchwork-notify@kernel.org>
Date:   Mon, 22 Mar 2021 20:20:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     davem@...emloft.net, kuba@...nel.org, netdev@...r.kernel.org,
        roopa@...dia.com, nikolay@...dia.com, vladimir.oltean@....com
Subject: Re: [PATCH net-next] net: bridge: declare br_vlan_tunnel_lookup argument
 tunnel_id as __be64

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Mon, 22 Mar 2021 12:38:19 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
> 
> The only caller of br_vlan_tunnel_lookup, br_handle_ingress_vlan_tunnel,
> extracts the tunnel_id from struct ip_tunnel_info::struct ip_tunnel_key::
> tun_id which is a __be64 value.
> 
> The exact endianness does not seem to matter, because the tunnel id is
> just used as a lookup key for the VLAN group's tunnel hash table, and
> the value is not interpreted directly per se. Moreover,
> rhashtable_lookup_fast treats the key argument as a const void *.
> 
> [...]

Here is the summary with links:
  - [net-next] net: bridge: declare br_vlan_tunnel_lookup argument tunnel_id as __be64
    https://git.kernel.org/netdev/net-next/c/f5fcca89f59c

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