public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: cxgb4 missing error handling?
Date: Wed, 04 Aug 2010 16:27:07 -0500	[thread overview]
Message-ID: <4C59DB2B.5050700@opengridcomputing.com> (raw)
In-Reply-To: <adafwyu6pt0.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>

On 08/04/2010 04:17 PM, Roland Dreier wrote:
> in cm.c we have:
>
> int c4iw_reject_cr(struct iw_cm_id *cm_id, const void *pdata, u8 pdata_len)
> {
> 	int err;
> 	struct c4iw_ep *ep = to_ep(cm_id);
> 	PDBG("%s ep %p tid %u\n", __func__, ep, ep->hwtid);
>
> 	if (state_read(&ep->com) == DEAD) {
> 		c4iw_put_ep(&ep->com);
> 		return -ECONNRESET;
> 	}
> 	BUG_ON(state_read(&ep->com) != MPA_REQ_RCVD);
> 	if (mpa_rev == 0)
> 		abort_connection(ep, NULL, GFP_KERNEL);
> 	else {
> 		err = send_mpa_reject(ep, pdata, pdata_len);
> 		err = c4iw_ep_disconnect(ep, 0, GFP_KERNEL);
> 	}
> 	c4iw_put_ep(&ep->com);
> 	return 0;
> }
>
> latest gcc warns that the variable err is assigned to but never used --
> and indeed it seems this code either should be doing something in the
> failure case or not even storing the return value if it doesn't care.
>
> Which one is it though?
>
>   - R.
>    

Good question. :)

I think we should get rid of 'err' altogether and ignore return values 
from send_mpa_reject() and c4iw_ep_disconnect().




--
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

      parent reply	other threads:[~2010-08-04 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 21:17 cxgb4 missing error handling? Roland Dreier
     [not found] ` <adafwyu6pt0.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-08-04 21:27   ` Steve Wise [this message]

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=4C59DB2B.5050700@opengridcomputing.com \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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