[lkml]   [2019]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] nvme-pci: Prevent mmio reads if pci channel offline
On 2/27/2019 10:42 AM, Gagniuc, Alexandru - Dell Team wrote:
> On 2/26/19 7:02 PM, Linus Torvalds wrote:
>> On Tue, Feb 26, 2019 at 2:37 PM <> wrote:
>>> Then nobody gets the (error) message. You can go a bit further and try
>>> 'pcie_ports=native". Again, nobody gets the memo. ):
>> So? The error was bogus to begin with. Why would we care?
> Of course nobody cares about that. We care about actual errors that we
> now know we won't be notified of. Imagine if we didn't get the memo that
> a piece of data is corrupt, and imagine the reaction of RAS folk.
> And I know the counter to that is a panic() is much more likely to cause
> data corruption, and we're trading one piece of crap for an even
> stinkier one. Whatever we end up doing, we have to do better than
> silence errors and pretend nothing happened.
>> Yes, yes, PCI bridges have the ability to return errors in accesses to
>> non-existent devices. But that was always bogus, and is never useful.
>> The whole "you get an interrupt or NMI on a bad access" is simply a
>> horribly broken model. It's not useful.
>> We already have long depended on hotplug drivers noticing the "oh, I'm
>> getting all-ff returns, the device may be gone". It's usually trivial,
>> and works a whole lot better.
> And that's been working great, hasn't it? I think you're thinking
> strictly about hotplug. There are other situations where things are all
> F'd, but the hardware isn't sending all F's. (example: ECRC errors)
>> It's not an error. Trying to force it to be an NMI or SCI or machine
>> check is bogus. It causes horrendous pain, because asynchronous
>> reporting doesn't work reliably anyway, and *synchronous* reporting is
>> impossible to sanely handle without crazy problems.
>> So the only sane model for hotplug devices is "IO still works, and
>> returns all ones". Maybe with an async one-time and *recoverable*
>> machine check or other reporting the access after the fact.
> Exactly!!! A notification (not calling it an 'error') that something
> unusual has happened is good. Treating these things like errors is so
> obvious, even a caveman wouldn't do it.
> In a world with FFS, we don't always get to have that model. Oh, FFS!
>> Anything else is simply broken. It would be broken even if firmware
>> wasn't involved, but obviously firmware people tend to often make a
>> bad situation even worse.
> Linus, be nice to firmware people. I've met a few, and I can vouch that
> they're very kind and nice. They're also very scared, especially when OS
> people want to ask them a few questions.
> I think FFS should get out of the way when OS advertises it's capable of
> handling XYZ. There are some good arguments why this hasn't happened,
> but I won't get into details. I do think it's unlikely that machines
> will be moving back to an OS-controlled model.
> And Linus, keep in mind, when these machines were developed, OSes
> couldn't handle recovery properly. None of this was ever an issue. It's
> our fault that we've changed the OS after the machines are on the market.

Just to add some background on these particular systems... at the time
they were designed none of the Linux distros we use supported the PCI
Error Recovery Services or maybe they did and we simply didn't know
about it. We found out rather by accident after the systems were
shipped that Linux had this ability. It was a pleasant surprise as
we've been asking OSVs to try to recover from PCI/PCIe errors for years.
Linux is the first (and still only) OS we use that can has a PCIe
error recovery model so kudos on that!

100% agree that crashing the system on PCIe errors like this is terrible
and we want to get to a recovery model. It was too late for the
generation of systems being discussed as it is a big paradigm shift and
lots of changes/validation that folks are not comfortable doing on
shipping products. But it's coming in future products.

We also noticed that there was no mechanism in the recovery models for
system firmware and OS to interact and come to know if recovery services
are available and no way for OS to inform platform if error recovery was
successful or not and no way to establish control of Downstream Port
Containment. This model - which PCI-SIG is calling Containment Error
Recovery - has been added in the relevant PCI-SIG documents and ACPI
spec and I believe Intel will start pushing patches soon. Hopefully
this will provide the industry standard solution needed to get to a full
error recovery model for PCIe-related errors.

There are other hardware additions in PCIe that could help with
synchronizing errors such as the RP PIO synchronous exception handling
added to PCIe as part of eDPC. Hardware is sparse but shipping AMD
Naples products already support this new hardware. I expect more
hardware to support as the industry shifts to Downstream Port
Containment/Containment Error Recovery model.

For these issues on existing platforms, I'm not sure what could be done.
Continuing to crash may be necessary until the CER solution is in place.

BTW, this patch in particular is complaining about an error for a
removed device. The Dell servers referenced in this chain will check if
the device is removed and if so it will suppress the error so I don't
think they are susceptible to this particular issue and I agree it is
broken if they do. If that is the case we can and will fix it in firmware.

> Alex
> _______________________________________________
> Linux-nvme mailing list

 \ /
  Last update: 2019-02-27 18:57    [W:0.099 / U:2.740 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site