netdev - Re: [PATCH net-next] net: bridge: fix undefined br_vlan_can_enter

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: <20200713.112311.1759350279713109431.davem@davemloft.net>
Date:   Mon, 13 Jul 2020 11:23:11 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     nikolay@...ulusnetworks.com
Cc:     netdev@...r.kernel.org, roopa@...ulusnetworks.com,
        sfr@...b.auug.org.au
Subject: Re: [PATCH net-next] net: bridge: fix undefined
 br_vlan_can_enter_range in tunnel code

From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Date: Mon, 13 Jul 2020 10:55:46 +0300

> If bridge vlan filtering is not defined we won't have
> br_vlan_can_enter_range and thus will get a compile error as was
> reported by Stephen and the build bot. So let's define a stub for when
> vlan filtering is not used.
> 
> Fixes: 94339443686b ("net: bridge: notify on vlan tunnel changes done via the old api")
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Signed-off-by: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>

Applied, thanks for fixing this.