From: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [bug report] IB/qib: Add new qib driver for QLogic PCIe InfiniBand adapters
Date: Wed, 25 Oct 2017 11:42:19 +0300 [thread overview]
Message-ID: <20171025084219.osbhmfytsoevzh7f@mwanda> (raw)
Hello Ralph Campbell,
The patch f931551bafe1: "IB/qib: Add new qib driver for QLogic PCIe
InfiniBand adapters" from May 23, 2010, leads to the following static
checker warning:
drivers/infiniband/hw/qib/qib_iba6120.c:1108 handle_6120_errors()
warn: was expecting a 64 bit value instead of '0'
drivers/infiniband/hw/qib/qib_iba6120.c
1100 /*
1101 * If there were hdrq or egrfull errors, wake up any processes
1102 * waiting in poll. We used to try to check which contexts had
1103 * the overflow, but given the cost of that and the chip reads
1104 * to support it, it's better to just wake everybody up if we
1105 * get an overflow; waiters can poll again if it's not them.
1106 */
1107 if (errs & (ERR_MASK(RcvEgrFullErr) | ERR_MASK(RcvHdrFullErr))) {
1108 qib_handle_urcv(dd, ~0U);
^^^
qib_handle_urcv() takes a u64 so we would sort of expect that we want
to pass U64_MAX here instead of U32_MAX. If it's intentional, then it's
pretty subtle.
1109 if (errs & ERR_MASK(RcvEgrFullErr))
1110 qib_stats.sps_buffull++;
1111 else
1112 qib_stats.sps_hdrfull++;
1113 }
1114 done:
1115 return;
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-10-25 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 8:42 Dan Carpenter [this message]
2017-10-25 8:59 ` [bug report] IB/qib: Add new qib driver for QLogic PCIe InfiniBand adapters Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2017-11-22 9:32 Dan Carpenter
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=20171025084219.osbhmfytsoevzh7f@mwanda \
--to=dan.carpenter-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ralph.campbell-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.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