netdev - Re: [net-next PATCH 0/3] Retrieve number of VFs in a bus-agnostic way

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

Message-Id: <20170120.114346.786441265338417344.davem@davemloft.net>
Date:   Fri, 20 Jan 2017 11:43:46 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     phil@....cc
Cc:     bhelgaas@...gle.com, netdev@...r.kernel.org,
        linux-pci@...r.kernel.org
Subject: Re: [net-next PATCH 0/3] Retrieve number of VFs in a bus-agnostic
 way

From: Phil Sutter <phil@....cc>
Date: Wed, 18 Jan 2017 14:04:36 +0100

> Previously, it was assumed that only PCI NICs would be capable of having
> virtual functions - with my proposed enhancement of dummy NIC driver
> implementing (fake) ones for testing purposes, this is no longer true.
> 
> Discussion of said patch has led to the suggestion of implementing a
> bus-agnostic method for VF count retrieval so rtnetlink could work with
> both real VF-capable PCI NICs as well as my dummy modifications without
> introducing ugly hacks.
> 
> The following series tries to achieve just that by introducing a bus
> type callback to retrieve a device's number of VFs, implementing this
> callback for PCI bus and finally adjusting rtnetlink to make use of the
> generalized infrastructure.

This is really nice and clean, compare it to your original approach :-)

Series applied, thanks!