linux-kernel - [PATCH v2 0/2] pci: ACS check fixes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130607162732.7733.17758.stgit@bling.home>
Date:	Fri, 07 Jun 2013 10:34:35 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	bhelgaas@...gle.com
Cc:	linux-pci@...r.kernel.org, ddutile@...hat.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] pci: ACS check fixes

After some further discussion, Don has come around to agreeing that
we cannot assume anything about devices which do not include an ACS
capability.  Patch 1 of this series is therefore the same as sent
before.  We have figured out though that some vendors are indicating
that they don't support peer-to-peer by providing an ACS capability
that is zero'd (ie. no capabilities).  This makes sense as ACS is
largely for allowing control of peer-to-peer features and almost all
of the individual capabilities are optional for multifunction
devices that do not support peer-to-peer.  This also simplifies our
flags filtering.  I'm hoping we'll soon have some quirks for devices
that do not support peer-to-peer, but also do not provide an ACS
capability.  Thanks,

Alex

---

Alex Williamson (2):
      pci: Fix flaw in pci_acs_enabled()
      pci: Differentiate ACS controllable from enabled

 drivers/pci/pci.c |   68 +++++++++++++++++++++++++++++++++++++++++------------
 1 file changed, 52 insertions(+), 16 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/