From: Hannes Reinecke <hare@suse.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Babu Moger <babu.moger@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/3] PCI VPD access fixes
Date: Tue, 12 Jan 2016 15:42:27 +0100 [thread overview]
Message-ID: <1452609750-90760-1-git-send-email-hare@suse.de> (raw)
Hi all,
the current PCI VPD page access assumes that the entire possible VPD
data is readable. However, the spec only guarantees a VPD data up to
the 'end' marker, with everything beyond that being undefined.
This causes a system lockup on certain devices.
With this patch we calculate the actual VPD size, or set it to '0'
if no valid VPD data could be read.
Hannes Reinecke (3):
pci: Update VPD definitions
pci: Update VPD size with correct length
pci: set VPD size to '0' if PCI_VPD_FLAGS_VPD_REF_F0 is set
drivers/pci/access.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++-
drivers/pci/pci-sysfs.c | 20 +++++++++------
include/linux/pci.h | 27 ++++++++++++++++++--
3 files changed, 104 insertions(+), 11 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-01-12 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 14:42 Hannes Reinecke [this message]
2016-01-12 14:42 ` [PATCH 1/3] pci: Update VPD definitions Hannes Reinecke
2016-01-12 14:42 ` [PATCH 2/3] pci: Update VPD size with correct length Hannes Reinecke
2016-01-12 14:42 ` [PATCH 3/3] pci: set VPD size to '0' if PCI_VPD_FLAGS_VPD_REF_F0 is set Hannes Reinecke
2016-01-12 17:23 ` [PATCH 0/3] PCI VPD access fixes Babu Moger
2016-01-12 22:15 ` Babu Moger
2016-01-13 8:20 ` Hannes Reinecke
2016-01-13 18:54 ` Babu Moger
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=1452609750-90760-1-git-send-email-hare@suse.de \
--to=hare@suse.de \
--cc=alexander.duyck@gmail.com \
--cc=babu.moger@oracle.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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).