From: Hannes Reinecke <hare@suse.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@suse.de>,
Alexander Duyck <alexander.h.duyck@redhat.com>,
Michal Kubecek <mkubecek@suse.com>
Subject: [PATCH] pci: Update VPD size with correct length
Date: Wed, 16 Dec 2015 11:28:43 +0100 [thread overview]
Message-ID: <1450261723-43658-1-git-send-email-hare@suse.de> (raw)
PCI-2.2 VPD entries have a maximum size of 32k, but might actually
be smaller than that. To figure out the actual size one has to read
the VPD area until the 'end marker' is reached.
Trying to read VPD data beyond that marker results in 'interesting'
effects, from simple read errors to crashing the card. And to make
matters worse not every PCI card implements this properly, leaving
us with no 'end' marker or even completely invalid data.
This path modifies the size of the VPD attribute to the available
size, and disables the VPD attribute altogether if no valid data
could be read.
Cc: Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: Michal Kubecek <mkubecek@suse.com>
Signed-off-by: Hannes Reinecke <hare@suse.de>
---
drivers/pci/access.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --git a/drivers/pci/access.c b/drivers/pci/access.c
index 59ac36f..afa86d6 100644
--- a/drivers/pci/access.c
+++ b/drivers/pci/access.c
@@ -475,6 +475,48 @@ static const struct pci_vpd_ops pci_vpd_f0_ops = {
.release = pci_vpd_pci22_release,
};
+/**
+ * pci_vpd_size - determine actual size of Vital Product Data
+ * @dev: pci device struct
+ * @old_size: current assumed size, also maximum allowed size
+ *
+ */
+static size_t
+pci_vpd_pci22_size(struct pci_dev *dev, size_t old_size)
+{
+ size_t off = 0;
+ unsigned char header[1+2]; /* 1 byte tag, 2 bytes length */
+
+ while (off < old_size && pci_read_vpd(dev, off, 1, header)) {
+ unsigned char tag;
+
+ if (header[0] == 0xff) {
+ /* Invalid data from VPD read */
+ tag = header[0];
+ } else if (header[0] & 0x80) {
+ /* Large Resource Data Type Tag */
+ if (pci_read_vpd(dev, off+1, 2, &header[1]) != 2)
+ return off + 1;
+ off += 3 + ((header[2] << 8) | header[1]);
+ tag = (header[0] & 0x7f);
+ } else {
+ /* Short Resource Data Type Tag */
+ off += 1 + (header[0] & 0x07);
+ tag = (header[0] & 0x78) >> 3;
+ }
+ if (tag == 0x0f) /* End tag descriptor */
+ break;
+ if ((tag != 0x02) && (tag != 0x10) && (tag != 0x11)) {
+ dev_debug(&dev->dev,
+ "invalid %s vpd tag %02x at offset %zu.",
+ header[0] & 0x80 ? "large" : "short",
+ tag, off);
+ break;
+ }
+ }
+ return off;
+}
+
int pci_vpd_pci22_init(struct pci_dev *dev)
{
struct pci_vpd_pci22 *vpd;
@@ -497,6 +539,13 @@ int pci_vpd_pci22_init(struct pci_dev *dev)
vpd->cap = cap;
vpd->busy = false;
dev->vpd = &vpd->base;
+ vpd->base.len = pci_vpd_pci22_size(dev, vpd->base.len);
+ if (vpd->base.len == 0) {
+ dev_debug(&dev->dev, "Disabling VPD access.");
+ dev->vpd = NULL;
+ kfree(vpd);
+ return -ENXIO;
+ }
return 0;
}
--
1.8.5.6
next reply other threads:[~2015-12-16 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 10:28 Hannes Reinecke [this message]
2015-12-16 10:41 ` [PATCH] pci: Update VPD size with correct length kbuild test robot
-- strict thread matches above, loose matches on Subject: below --
2015-10-23 9:09 Hannes Reinecke
2015-10-23 10:47 ` kbuild test robot
2015-10-24 0:52 ` Alexander Duyck
2015-10-25 3:34 ` Hannes Reinecke
2015-11-25 17:17 ` Bjorn Helgaas
2015-11-25 18:01 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1450261723-43658-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=alexander.h.duyck@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mkubecek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).