netdev - Re: [PATCH net] vrf: prevent adding upper devices

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: <20190327.225709.1473738504192443406.davem@davemloft.net>
Date:   Wed, 27 Mar 2019 22:57:09 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     sd@...asysnail.net
Cc:     netdev@...r.kernel.org, dsahern@...il.com
Subject: Re: [PATCH net] vrf: prevent adding upper devices

From: Sabrina Dubroca <sd@...asysnail.net>
Date: Tue, 26 Mar 2019 18:22:16 +0100

> VRF devices don't work with upper devices. Currently, it's possible to
> add a VRF device to a bridge or team, and to create macvlan, macsec, or
> ipvlan devices on top of a VRF (bond and vlan are prevented respectively
> by the lack of an ndo_set_mac_address op and the NETIF_F_VLAN_CHALLENGED
> feature flag).
> 
> Fix this by setting the IFF_NO_RX_HANDLER flag (introduced in commit
> f5426250a6ec ("net: introduce IFF_NO_RX_HANDLER")).
> 
> Cc: David Ahern <dsahern@...il.com>
> Fixes: 193125dbd8eb ("net: Introduce VRF device driver")
> Signed-off-by: Sabrina Dubroca <sd@...asysnail.net>

Applied and queued up for -stable, thanks.