From: Bjorn Helgaas <helgaas@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Hannes Reinecke <hare@suse.de>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: [PATCH 0/5] PCI/VPD: pci_vpd_size() cleanups
Date: Thu, 15 Jul 2021 16:59:54 -0500 [thread overview]
Message-ID: <20210715215959.2014576-1-helgaas@kernel.org> (raw)
In-Reply-To: <dc566e6c-4c9b-bcd5-1f33-edba94cedd00@gmail.com>
From: Bjorn Helgaas <bhelgaas@google.com>
This is a follow-up to the conversation here:
https://lore.kernel.org/r/1cdda5f1-e1ea-af9f-cfbe-952b7d37e246@gmail.com
about how and whether we should validate the contents of VPD.
My proposal is to basically do minimal validation since the kernel really
doesn't care about the actual *contents* of VPD and mainly provides an
access mechanism (although there a few drivers that get part numbers and
maybe even clocking information from VPD).
I welcome any feedback!
Bjorn Helgaas (5):
PCI/VPD: Correct diagnostic for VPD read failure
PCI/VPD: Check Resource tags against those valid for type
PCI/VPD: Consolidate missing EEPROM checks
PCI/VPD: Don't check Large Resource types for validity
PCI/VPD: Allow access to valid parts of VPD if some is invalid
drivers/pci/vpd.c | 63 +++++++++++++++++++++++++----------------------
1 file changed, 33 insertions(+), 30 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-07-15 22:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 20:53 [PATCH 0/5] PCI/VPD: Further improvements Heiner Kallweit
2021-05-13 20:55 ` [PATCH 2/5] PCI: Clean up VPD constants and functions in pci.h Heiner Kallweit
2021-07-14 16:43 ` Bjorn Helgaas
2021-05-13 20:56 ` [PATCH 3/5] PCI/VPD: Remove old_size argument from pci_vpd_size Heiner Kallweit
2021-05-13 20:56 ` [PATCH 4/5] PCI/VPD: Make pci_vpd_wait uninterruptible Heiner Kallweit
2021-05-13 20:58 ` [PATCH 1/5] PCI/VPD: Refactor pci_vpd_size Heiner Kallweit
2021-07-13 20:25 ` Bjorn Helgaas
2021-07-13 21:13 ` Heiner Kallweit
2021-07-14 15:50 ` Bjorn Helgaas
2021-07-15 8:31 ` Heiner Kallweit
2021-05-13 21:02 ` [PATCH 5/5] PCI/VPD: Remove pci_vpd member flag Heiner Kallweit
2021-07-06 5:56 ` [PATCH 0/5] PCI/VPD: Further improvements Heiner Kallweit
2021-07-06 14:32 ` Bjorn Helgaas
2021-07-15 21:59 ` Bjorn Helgaas [this message]
2021-07-15 21:59 ` [PATCH 1/5] PCI/VPD: Correct diagnostic for VPD read failure Bjorn Helgaas
2021-07-15 22:07 ` Heiner Kallweit
2021-07-16 5:58 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 2/5] PCI/VPD: Check Resource tags against those valid for type Bjorn Helgaas
2021-07-16 5:59 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 3/5] PCI/VPD: Consolidate missing EEPROM checks Bjorn Helgaas
2021-07-15 22:16 ` Heiner Kallweit
2021-07-28 23:42 ` Bjorn Helgaas
2021-07-29 6:10 ` Heiner Kallweit
2021-07-29 18:31 ` Bjorn Helgaas
2021-07-16 6:00 ` Hannes Reinecke
2021-07-15 21:59 ` [PATCH 4/5] PCI/VPD: Don't check Large Resource types for validity Bjorn Helgaas
2021-07-16 6:03 ` Hannes Reinecke
2021-07-28 23:46 ` Bjorn Helgaas
2021-07-15 21:59 ` [PATCH 5/5] PCI/VPD: Allow access to valid parts of VPD if some is invalid Bjorn Helgaas
2021-07-16 6:04 ` Hannes Reinecke
2021-08-02 22:32 ` [PATCH 0/5] PCI/VPD: Further improvements Bjorn Helgaas
2021-08-05 19:10 ` Heiner Kallweit
2021-08-05 19:29 ` Bjorn Helgaas
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=20210715215959.2014576-1-helgaas@kernel.org \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=hare@suse.de \
--cc=hkallweit1@gmail.com \
--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).