From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: [bug report] Add support of Cavium Liquidio ethernet adapters
Date: Wed, 30 Nov 2016 18:57:55 +0000 [thread overview]
Message-ID: <20161130185754.GA8645@mwanda> (raw)
Hello Raghu Vatsavayi,
The patch f21fb3ed364b: "Add support of Cavium Liquidio ethernet
adapters" from Jun 9, 2015, leads to the following static checker
warning:
drivers/net/ethernet/cavium/liquidio/lio_main.c:1013 liquidio_schedule_droq_pkt_handlers()
warn: potential left shift more than type allows '0-63'
drivers/net/ethernet/cavium/liquidio/lio_main.c
996 static void liquidio_schedule_droq_pkt_handlers(struct octeon_device *oct)
997 {
998 struct octeon_device_priv *oct_priv 999 (struct octeon_device_priv *)oct->priv;
1000 u64 oq_no;
This should probably be int. Making it u64 doesn't do anything.
1001 struct octeon_droq *droq;
1002
1003 if (oct->int_status & OCT_DEV_INTR_PKT_DATA) {
1004 for (oq_no = 0; oq_no < MAX_OCTEON_OUTPUT_QUEUES(oct);
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is either 32 or 64.
1005 oq_no++) {
1006 if (!(oct->droq_intr & BIT_ULL(oq_no)))
1007 continue;
1008
1009 droq = oct->droq[oq_no];
1010
1011 if (droq->ops.poll_mode) {
1012 droq->ops.napi_fn(droq);
1013 oct_priv->napi_mask |= (1 << oq_no);
It should be 1ULL << oq_no. But the other bug is tahte ->napi_mask is
a long but that will break on 32 bit systems when MAX_OCTEON_OUTPUT_QUEUES()
is 64. Is that a possible combination?
1014 } else {
1015 tasklet_schedule(&oct_priv->droq_tasklet);
1016 }
1017 }
1018 }
1019 }
regards,
dan carpenter
next reply other threads:[~2016-11-30 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 18:57 Dan Carpenter [this message]
2016-11-30 19:02 ` [bug report] Add support of Cavium Liquidio ethernet adapters Vatsavayi, Raghu
2016-11-30 19:26 ` 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=20161130185754.GA8645@mwanda \
--to=dan.carpenter@oracle.com \
--cc=kernel-janitors@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).