From: Vladis Dronov <vdronov@redhat.com>
To: linux-pci@vger.kernel.org
Cc: Vladis Dronov <vdronov@redhat.com>
Subject: [PATCH] PCI: fix invalid ROM content detection in pci_get_rom_size()
Date: Fri, 6 Nov 2015 13:16:36 +0100 [thread overview]
Message-ID: <1446812196-3497-1-git-send-email-vdronov@redhat.com> (raw)
Make pci_get_rom_size() to check all bytes in the PCI ROM signature
and issue a warning if the values are not following the standard.
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
---
drivers/pci/rom.c | 17 ++++++-----------
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/pci/rom.c b/drivers/pci/rom.c
index eb0ad53..34f8b2c 100644
--- a/drivers/pci/rom.c
+++ b/drivers/pci/rom.c
@@ -77,22 +77,17 @@ size_t pci_get_rom_size(struct pci_dev *pdev, void __iomem *rom, size_t size)
do {
void __iomem *pds;
/* Standard PCI ROMs start out with these bytes 55 AA */
- if (readb(image) != 0x55) {
- dev_err(&pdev->dev, "Invalid ROM contents\n");
+ if ((readb(image) != 0x55) || (readb(image + 1) != 0xAA)) {
+ dev_err(&pdev->dev, "Invalid PCI ROM signature\n");
break;
}
- if (readb(image + 1) != 0xAA)
- break;
/* get the PCI data structure and check its signature */
pds = image + readw(image + 24);
- if (readb(pds) != 'P')
- break;
- if (readb(pds + 1) != 'C')
- break;
- if (readb(pds + 2) != 'I')
- break;
- if (readb(pds + 3) != 'R')
+ if ((readb(pds) != 'P') || (readb(pds + 1) != 'C') ||
+ (readb(pds + 2) != 'I') || (readb(pds + 3) != 'R')) {
+ dev_err(&pdev->dev, "Invalid PCI ROM data signature\n");
break;
+ }
last_image = readb(pds + 21) & 0x80;
length = readw(pds + 16);
image += length * 512;
--
2.6.2
next reply other threads:[~2015-11-06 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 12:16 Vladis Dronov [this message]
2015-11-24 17:03 ` [PATCH] PCI: fix invalid ROM content detection in pci_get_rom_size() Bjorn Helgaas
2015-11-27 17:05 ` Vladis Dronov
2015-11-27 17:20 ` [PATCH v2] PCI: fix missing ROM content warning " Vladis Dronov
2015-12-04 23:44 ` 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=1446812196-3497-1-git-send-email-vdronov@redhat.com \
--to=vdronov@redhat.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).