From: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH for-next 1/2] IB/core: Fix build warnings
Date: Thu, 31 Oct 2013 10:02:39 -0700 [thread overview]
Message-ID: <52728D2F.4020301@acm.org> (raw)
In-Reply-To: <1383236511-4337-2-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On 31/10/2013 9:21, Or Gerlitz wrote:
> Fix the below few "make W=1" build warnings we have on the IB core.
>
> drivers/infiniband/core/sysfs.c: In function ‘state_show’:
> drivers/infiniband/core/sysfs.c:107: warning: comparison of unsigned expression >= 0 is always true
> drivers/infiniband/core/verbs.c: In function ‘ib_modify_qp_is_ok’:
> drivers/infiniband/core/verbs.c:783: warning: comparison of unsigned expression < 0 is always false
> drivers/infiniband/core/verbs.c:784: warning: comparison of unsigned expression < 0 is always false
> drivers/infiniband/core/iwcm.c: In function ‘destroy_cm_id’:
> drivers/infiniband/core/iwcm.c:330: warning: variable ‘ret’ set but not used
>
> Signed-off-by: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
> ---
> drivers/infiniband/core/iwcm.c | 2 --
> drivers/infiniband/core/sysfs.c | 2 +-
> drivers/infiniband/core/verbs.c | 3 +--
> 3 files changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/infiniband/core/iwcm.c b/drivers/infiniband/core/iwcm.c
> index c47c203..ab8ebf8 100644
> --- a/drivers/infiniband/core/iwcm.c
> +++ b/drivers/infiniband/core/iwcm.c
> @@ -327,7 +327,6 @@ static void destroy_cm_id(struct iw_cm_id *cm_id)
> {
> struct iwcm_id_private *cm_id_priv;
> unsigned long flags;
> - int ret;
>
> cm_id_priv = container_of(cm_id, struct iwcm_id_private, id);
> /*
> @@ -343,7 +342,6 @@ static void destroy_cm_id(struct iw_cm_id *cm_id)
> cm_id_priv->state = IW_CM_STATE_DESTROYING;
> spin_unlock_irqrestore(&cm_id_priv->lock, flags);
> /* destroy the listening endpoint */
> - ret = cm_id->device->iwcm->destroy_listen(cm_id);
> spin_lock_irqsave(&cm_id_priv->lock, flags);
> break;
> case IW_CM_STATE_ESTABLISHED:
> diff --git a/drivers/infiniband/core/sysfs.c b/drivers/infiniband/core/sysfs.c
> index cde1e7b..1184050 100644
> --- a/drivers/infiniband/core/sysfs.c
> +++ b/drivers/infiniband/core/sysfs.c
> @@ -104,7 +104,7 @@ static ssize_t state_show(struct ib_port *p, struct port_attribute *unused,
> return ret;
>
> return sprintf(buf, "%d: %s\n", attr.state,
> - attr.state >= 0 && attr.state < ARRAY_SIZE(state_name) ?
> + attr.state < ARRAY_SIZE(state_name) ?
> state_name[attr.state] : "UNKNOWN");
> }
>
> diff --git a/drivers/infiniband/core/verbs.c b/drivers/infiniband/core/verbs.c
> index a321df2..7b0c1f4 100644
> --- a/drivers/infiniband/core/verbs.c
> +++ b/drivers/infiniband/core/verbs.c
> @@ -780,8 +780,7 @@ int ib_modify_qp_is_ok(enum ib_qp_state cur_state, enum ib_qp_state next_state,
> {
> enum ib_qp_attr_mask req_param, opt_param;
>
> - if (cur_state < 0 || cur_state > IB_QPS_ERR ||
> - next_state < 0 || next_state > IB_QPS_ERR)
> + if (cur_state > IB_QPS_ERR || next_state > IB_QPS_ERR)
> return 0;
>
> if (mask & IB_QP_CUR_STATE &&
>
I agree that removing unused variables is good because it makes source
code easier to read. However, removing the "attr.state >= 0" check from
state_show() looks dangerous to me. If the type of that variable would
ever be changed from unsigned to signed then that would break
state_show() in a very subtle way. It could take a long time before such
breakage is detected. How about modifying the behavior of W=1 such that
it doesn't warn about comparisons that are always true (-Wno-type-limits) ?
Bart.
--
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 prev parent reply other threads:[~2013-10-31 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 16:21 [PATCH for-next 0/2] Fix build warnings Or Gerlitz
[not found] ` <1383236511-4337-1-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 16:21 ` [PATCH for-next 1/2] IB/core: " Or Gerlitz
[not found] ` <1383236511-4337-2-git-send-email-ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-10-31 17:02 ` Bart Van Assche [this message]
[not found] ` <52728D2F.4020301-HInyCGIudOg@public.gmane.org>
2013-10-31 19:28 ` David Dillow
[not found] ` <1383247739.2110.7.camel-a7a0dvSY7KqLUyTwlgNVppKKF0rrzTr+@public.gmane.org>
2013-11-03 8:22 ` Or Gerlitz
2013-10-31 17:59 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237388CF3CA4-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-10-31 19:44 ` Or Gerlitz
2013-10-31 16:21 ` [PATCH for-next 2/2] IB/mlx4: " Or Gerlitz
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=52728D2F.4020301@acm.org \
--to=bvanassche-hinycgiudog@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@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