From: David Miller <davem@davemloft.net>
To: ajit.khaparde@emulex.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] be2net: Ignore spurious UE indication from NIC
Date: Fri, 21 Sep 2012 15:04:13 -0400 (EDT) [thread overview]
Message-ID: <20120921.150413.2303624982785706643.davem@davemloft.net> (raw)
In-Reply-To: <20120921163620.GA6147@akhaparde-VBox>
From: Ajit Khaparde <ajit.khaparde@emulex.com>
Date: Fri, 21 Sep 2012 11:36:20 -0500
> Ignore spurious UE indication seen on some platforms.
> Consider the error as un-recoverable only when the bits
> stay high during second sampling.
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@emulex.com>
Treating uncorrectable errors as spurious seems like an invitation
for hard to track down data corruption to me.
You'll need to come up with a more sophisticated test for
spurious other than "happens more than once" before I'm willing
to subject the entire world to this kind of potential problem.
next prev parent reply other threads:[~2012-09-21 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 16:36 [PATCH net-next] be2net: Ignore spurious UE indication from NIC Ajit Khaparde
2012-09-21 19:04 ` David Miller [this message]
2012-09-26 22:35 ` Khaparde, Ajit
2012-09-26 23:33 ` David Miller
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=20120921.150413.2303624982785706643.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajit.khaparde@emulex.com \
--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;
as well as URLs for NNTP newsgroup(s).