From: David Miller <davem@davemloft.net>
To: gpiccoli@linux.vnet.ibm.com
Cc: ariel.elior@cavium.com, everest-linux-l2@cavium.com,
netdev@vger.kernel.org, gpiccoli@protonmail.ch
Subject: Re: [PATCH net] bnx2x: Improve reliability in case of nested PCI errors
Date: Wed, 27 Dec 2017 12:13:49 -0500 (EST) [thread overview]
Message-ID: <20171227.121349.689207304027894541.davem@davemloft.net> (raw)
In-Reply-To: <20171222150139.10244-1-gpiccoli@linux.vnet.ibm.com>
From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
Date: Fri, 22 Dec 2017 13:01:39 -0200
> While in recovery process of PCI error (called EEH on PowerPC arch),
> another PCI transaction could be corrupted causing a situation of
> nested PCI errors. Also, this scenario could be reproduced with
> error injection mechanisms (for debug purposes).
>
> We observe that in case of nested PCI errors, bnx2x might attempt to
> initialize its shmem and cause a kernel crash due to bad addresses
> read from MCP. Multiple different stack traces were observed depending
> on the point the second PCI error happens.
>
> This patch avoids the crashes by:
>
> * failing PCI recovery in case of nested errors (since multiple
> PCI errors in a row are not expected to lead to a functional
> adapter anyway), and by,
>
> * preventing access to adapter FW when MCP is failed (we mark it as
> failed when shmem cannot get initialized properly).
>
> Reported-by: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
> Signed-off-by: Guilherme G. Piccoli <gpiccoli@linux.vnet.ibm.com>
Applied, thank you.
prev parent reply other threads:[~2017-12-27 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 15:01 [PATCH net] bnx2x: Improve reliability in case of nested PCI errors Guilherme G. Piccoli
2017-12-27 6:24 ` Shaikh, Shahed
2017-12-27 17:13 ` David Miller [this message]
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=20171227.121349.689207304027894541.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@cavium.com \
--cc=everest-linux-l2@cavium.com \
--cc=gpiccoli@linux.vnet.ibm.com \
--cc=gpiccoli@protonmail.ch \
--cc=netdev@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