diff options
author | Qiang <zhengqiang10@huawei.com> | 2017-09-28 11:54:34 +0800 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2017-11-07 18:38:47 -0600 |
commit | 3ad3f8ce50914288731a3018b27ee44ab803e170 (patch) | |
tree | cda2e47477e1296ce050ba71fea678b141c3799c /arch/mn10300 | |
parent | 4113b0e60bf188c8a557c22f64294aa9c6019074 (diff) | |
download | linux-stable-3ad3f8ce50914288731a3018b27ee44ab803e170.tar.gz linux-stable-3ad3f8ce50914288731a3018b27ee44ab803e170.tar.bz2 linux-stable-3ad3f8ce50914288731a3018b27ee44ab803e170.zip |
PCI/PME: Handle invalid data when reading Root Status
PCIe PME and native hotplug share the same interrupt number, so hotplug
interrupts are also processed by PME. In some cases, e.g., a Link Down
interrupt, a device may be present but unreachable, so when we try to
read its Root Status register, the read fails and we get all ones data
(0xffffffff).
Previously, we interpreted that data as PCI_EXP_RTSTA_PME being set, i.e.,
"some device has asserted PME," so we scheduled pcie_pme_work_fn(). This
caused an infinite loop because pcie_pme_work_fn() tried to handle PME
requests until PCI_EXP_RTSTA_PME is cleared, but with the link down,
PCI_EXP_RTSTA_PME can't be cleared.
Check for the invalid 0xffffffff data everywhere we read the Root Status
register.
1469d17dd341 ("PCI: pciehp: Handle invalid data when reading from
non-existent devices") added similar checks in the hotplug driver.
Signed-off-by: Qiang Zheng <zhengqiang10@huawei.com>
[bhelgaas: changelog, also check in pcie_pme_work_fn(), use "~0" to follow
other similar checks]
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Diffstat (limited to 'arch/mn10300')
0 files changed, 0 insertions, 0 deletions