netdev - Re: [net-next PATCH v7] net: dummy: Introduce dummy virtual functions

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: <20170124.140742.2012452984177351042.davem@davemloft.net>
Date:   Tue, 24 Jan 2017 14:07:42 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     phil@....cc
Cc:     netdev@...r.kernel.org, sd@...asysnail.net
Subject: Re: [net-next PATCH v7] net: dummy: Introduce dummy virtual
 functions

From: Phil Sutter <phil@....cc>
Date: Mon, 23 Jan 2017 12:17:33 +0100

> The idea for this was born when testing VF support in iproute2 which was
> impeded by hardware requirements. In fact, not every VF-capable hardware
> driver implements all netdev ops, so testing the interface is still hard
> to do even with a well-sorted hardware shelf.
> 
> To overcome this and allow for testing the user-kernel interface, this
> patch allows to turn dummy into a PF with a configurable amount of VFs.
> 
> Since my patch series 'bus-agnostic-num-vf' has been accepted,
> implementing the required interfaces is pretty straightforward: Iff
> 'num_vfs' module parameter was given a value >0, a dummy bus type is
> being registered which implements the 'num_vf()' callback. Additionally,
> a dummy parent device common to all dummy devices is registered which
> sits on the above dummy bus.
> 
> Joint work with Sabrina Dubroca.
> 
> Signed-off-by: Sabrina Dubroca <sd@...asysnail.net>
> Signed-off-by: Phil Sutter <phil@....cc>

Yeah this looks awesome, applied, thanks!