From: David Gibson <david@gibson.dropbear.id.au>
To: manish.chopra@qlogic.com, sony.chacko@qlogic.com,
rajesh.borundia@qlogic.com
Cc: netdev@vger.kernel.org, snagarka@redhat.com, tcamuso@redhat.com,
vdasgupt@redhat.com
Subject: [0/2] netxen: bug fix and diagnostics for possible (hardware?) bug
Date: Tue, 17 Dec 2013 16:22:31 +1100 [thread overview]
Message-ID: <1387257753-18676-1-git-send-email-david@gibson.dropbear.id.au> (raw)
At Red Hat, we've hit a couple of customer cases with crashes in the
netxen driver due to list corruption. This seems to be very rarely
triggered, and unfortunately the dumps we have don't have enough
information to be certain of the cause, although we have a possible
theory.
I'm suggesting, therefore a patch to add some sanity checking which
should help to at least localize and mitigate the problem when someone
hits it in future. Please let me know if there's a better approach to
doing this.
That's 2/2. 1/2 is a fix for a clear bug I spotted along the way, but
not one that could cause the symptoms we've seen.
next reply other threads:[~2013-12-17 5:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 5:22 David Gibson [this message]
2013-12-17 5:22 ` [PATCH 1/2] netxen: Correct off-by-one error in bounds check David Gibson
2013-12-17 6:37 ` Jitendra Kalsaria
2013-12-19 11:51 ` Manish Chopra
2013-12-20 4:11 ` David Gibson
2013-12-17 5:22 ` [PATCH 2/2] netxen: Add sanity checks for Rx buffers returning from hardware David Gibson
2013-12-19 20:05 ` David Miller
2014-01-24 5:21 ` David Gibson
2013-12-17 21:50 ` [0/2] netxen: bug fix and diagnostics for possible (hardware?) bug Manish Chopra
2013-12-18 6:22 ` David Gibson
2013-12-19 9:11 ` Manish Chopra
2014-01-24 6:44 ` David Gibson
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=1387257753-18676-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=manish.chopra@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=rajesh.borundia@qlogic.com \
--cc=snagarka@redhat.com \
--cc=sony.chacko@qlogic.com \
--cc=tcamuso@redhat.com \
--cc=vdasgupt@redhat.com \
/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).