From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: linasvepstas@gmail.com, Cao jin <caoj.fnst@cn.fujitsu.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] pci-error-recover: doc cleanup
Date: Fri, 9 Dec 2016 17:50:17 +1100 [thread overview]
Message-ID: <3ed3151c-eeef-940c-8a9c-49cf53a51d49@au1.ibm.com> (raw)
In-Reply-To: <CAHrUA35PMscQrohN_wPgip2tM-+OiHmQT1_uhPc75=GeHvkpaw@mail.gmail.com>
On 09/12/16 17:24, Linas Vepstas wrote:
> I suppose I'm confused, but I recall that link resets are non-fatal.
> Fatal errors typically require that the the pci adapter be completely
> reset, any adapter firmware to be reloaded from scratch, the device
> driver has to kill all device state and start from scratch. Its huge.
Is there a difference in terminology between an AER fatal error and what
EEH/IBM people think of as a fatal error?
> If the fatal error is on pci device that is under a block device
> holding a file system, then (usually) there is no way to recover,
> because the block layer (and file system) cannot deal with a block
> device that disappeared and then reappeared some few seconds later.
> (maybe some future zfs or lvm or btrfs might be able to deal with
> this, but not today)
Is this still true? I'm not at all familiar with the block device side
of it, but the cxlflash driver has reasonably full EEH support,
including surviving a full PHB fence and complete reset.
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2016-12-09 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 8:16 Cao jin
2016-12-08 14:05 ` Jonathan Corbet
2016-12-08 14:13 ` Cao jin
2016-12-09 6:24 ` Linas Vepstas
2016-12-09 6:37 ` Cao jin
2016-12-09 6:44 ` Linas Vepstas
2016-12-09 7:59 ` Cao jin
2016-12-09 16:11 ` Alex Williamson
2016-12-09 14:37 ` Jonathan Corbet
2016-12-19 3:25 ` Cao jin
2016-12-09 6:50 ` Andrew Donnellan [this message]
2016-12-14 2:39 ` Gavin Shan
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=3ed3151c-eeef-940c-8a9c-49cf53a51d49@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=bhelgaas@google.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=corbet@lwn.net \
--cc=linasvepstas@gmail.com \
--cc=linux-doc@vger.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
all inboxes | Powered by JetHome®