From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 42142] New: mpt2sas: Number specified in wrong base.
Date: Wed, 31 Aug 2011 19:56:41 GMT [thread overview]
Message-ID: <bug-42142-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=42142
Summary: mpt2sas: Number specified in wrong base.
Product: SCSI Drivers
Version: 2.5
Kernel Version: 3.0.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Other
AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
ReportedBy: daniel.kernel@the-cell.co.uk
Regression: No
I think this is the right product/component combination, sorry if it isn't.
I was hunting through mpt2sas chasing unrelated hardware gremlins and noticed
an odd bit of code, I've checked the latest version on lxr and it's still
there.
http://lxr.linux.no/linux+v3.0.4/drivers/scsi/mpt2sas/mpt2sas_base.c#L611
611 /* eat the loginfos associated with task aborts */
612 if (ioc->ignore_loginfos && (log_info == 30050000 || log_info ==
613 0x31140000 || log_info == 0x31130000))
614 return;
615
I'm assuming that the first of those log_info checks is meant to be 0x30050000,
as specified it is rendered always false by the bus type check a few lines
above.
It's a minor detail, but I thought I'd report it anyway since it's so trivial
to fix if you have the source to hand.
Regards,
Daniel
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2011-08-31 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 19:56 bugzilla-daemon [this message]
2012-04-04 15:04 ` [Bug 42142] mpt2sas: Number specified in wrong base bugzilla-daemon
2012-06-13 15:12 ` bugzilla-daemon
2012-06-13 15:12 ` bugzilla-daemon
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=bug-42142-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).