linux-kernel - [PATCH 0/5] Various of SR-IOV fixes and cleanup

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

Date:	Tue, 27 Oct 2015 13:52:08 -0700
From:	Alexander Duyck <aduyck@...antis.com>
To:	bhelgaas@...gle.com
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] Various of SR-IOV fixes and cleanup

This patch set is meant to address several issues found in recent patches
currently in the pci/virtualization branch.

The first two patches address possible issues in initialization.
Specifically the fact that offset and stride cannot be read while numvfs is
0, and that the BARs need to be reset if totalVFs has increased because the
BIOS likely allocated the given resources under the assumption of a smaller
number of VFs being available.

The last 3 address a number of issues in sriov_enable.  They started as
just a patch to address the offset and stride issues, however there were
some other issues found related to pcibios_enable_sriov that I decided to
address as well, and then there was some minor cleanup in addition to all
of that.

---

Alexander Duyck (5):
      iov: Update virtfn_max_buses to validate offset and stride
      iov: Reset resources to 0 if totalVFs increases after enabling ARI
      iov: Fix sriov_enable exception handling path
      iov: Variable and loop cleanup for sriov_disable and sriov_enable
      iov: Update sriov_enable to correctly handle offset and stride

 drivers/pci/iov.c |  123 ++++++++++++++++++++++++++++-------------------------
 1 file changed, 65 insertions(+), 58 deletions(-)

--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/