All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	gregkh@linuxfoundation.org, jasowang@redhat.com,
	ohering@suse.com, jbottomley@parallels.com,
	linux-kernel@vger.kernel.org, hch@infradead.org,
	apw@canonical.com, devel@linuxdriverproject.org
Subject: Re: [PATCH 2/4] scsi: storvsc: Properly support Fibre Channel devices
Date: Fri, 11 Dec 2015 13:25:19 +0300	[thread overview]
Message-ID: <20151211102519.GF5284@mwanda> (raw)
In-Reply-To: <1449792860-15447-2-git-send-email-kys@microsoft.com>

On Thu, Dec 10, 2015 at 04:14:18PM -0800, K. Y. Srinivasan wrote:
> +	ret = vmbus_sendpacket(device->channel, vstor_packet,
> +			       (sizeof(struct vstor_packet) -
> +			       vmscsi_size_delta),
> +			       (unsigned long)request,
> +			       VM_PKT_DATA_INBAND,
> +			       VMBUS_DATA_PACKET_FLAG_COMPLETION_REQUESTED);
> +
> +	if (ret != 0)
> +		goto cleanup;
> +
> +	t = wait_for_completion_timeout(&request->wait_event, 5*HZ);
> +	if (t == 0) {
> +		ret = -ETIMEDOUT;
> +		goto cleanup;
> +	}
> +
> +	if (vstor_packet->operation != VSTOR_OPERATION_COMPLETE_IO ||
> +	    vstor_packet->status != 0)
> +		goto cleanup;

"cleanup" is a misleading name because it doesn't clean up anything.
Do nothing gotos are a pain in the butt and they always introduce bugs.
For example, you appear to have forgotten to set the error code.  But
because it's a do-nothing goto it's ambiguous so perhaps returning
success was intended.

Empirically this style of coding causes bugs.  It does not prevent them.
It is a bad style if you believe in measuring, evidence and science.

regards,
dan carpenter

WARNING: multiple messages have this Message-ID (diff)
From: Dan Carpenter <dan.carpenter@oracle.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	devel@linuxdriverproject.org, ohering@suse.com,
	jbottomley@parallels.com, hch@infradead.org,
	linux-scsi@vger.kernel.org, apw@canonical.com,
	vkuznets@redhat.com, jasowang@redhat.com,
	martin.petersen@oracle.com
Subject: Re: [PATCH 2/4] scsi: storvsc: Properly support Fibre Channel devices
Date: Fri, 11 Dec 2015 13:25:19 +0300	[thread overview]
Message-ID: <20151211102519.GF5284@mwanda> (raw)
In-Reply-To: <1449792860-15447-2-git-send-email-kys@microsoft.com>

On Thu, Dec 10, 2015 at 04:14:18PM -0800, K. Y. Srinivasan wrote:
> +	ret = vmbus_sendpacket(device->channel, vstor_packet,
> +			       (sizeof(struct vstor_packet) -
> +			       vmscsi_size_delta),
> +			       (unsigned long)request,
> +			       VM_PKT_DATA_INBAND,
> +			       VMBUS_DATA_PACKET_FLAG_COMPLETION_REQUESTED);
> +
> +	if (ret != 0)
> +		goto cleanup;
> +
> +	t = wait_for_completion_timeout(&request->wait_event, 5*HZ);
> +	if (t == 0) {
> +		ret = -ETIMEDOUT;
> +		goto cleanup;
> +	}
> +
> +	if (vstor_packet->operation != VSTOR_OPERATION_COMPLETE_IO ||
> +	    vstor_packet->status != 0)
> +		goto cleanup;

"cleanup" is a misleading name because it doesn't clean up anything.
Do nothing gotos are a pain in the butt and they always introduce bugs.
For example, you appear to have forgotten to set the error code.  But
because it's a do-nothing goto it's ambiguous so perhaps returning
success was intended.

Empirically this style of coding causes bugs.  It does not prevent them.
It is a bad style if you believe in measuring, evidence and science.

regards,
dan carpenter


  parent reply	other threads:[~2015-12-11 10:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  0:13 [PATCH 0/4] scsi: storvsc: Properly support FC hosts K. Y. Srinivasan
2015-12-11  0:14 ` [PATCH 1/4] scsi: storvsc: Fix a bug in the layout of the hv_fc_wwn_packet K. Y. Srinivasan
2015-12-11  0:14   ` K. Y. Srinivasan
2015-12-11  0:14   ` [PATCH 2/4] scsi: storvsc: Properly support Fibre Channel devices K. Y. Srinivasan
2015-12-11  0:14     ` K. Y. Srinivasan
2015-12-11  8:58     ` Johannes Thumshirn
2015-12-11  8:58       ` Johannes Thumshirn
2015-12-11 10:25     ` Dan Carpenter [this message]
2015-12-11 10:25       ` Dan Carpenter
2015-12-12  3:07       ` KY Srinivasan
2015-12-11  0:14   ` [PATCH 3/4] scsi: storvsc: Refactor the code in storvsc_channel_init() K. Y. Srinivasan
2015-12-11  0:14     ` K. Y. Srinivasan
2015-12-11  9:02     ` Johannes Thumshirn
2015-12-11 10:40     ` Dan Carpenter
2015-12-11 10:40       ` Dan Carpenter
2015-12-12  3:06       ` KY Srinivasan
2015-12-12  3:06         ` KY Srinivasan
2015-12-11  0:14   ` [PATCH 4/4] scsi: storvsc: Tighten up the interrupt path K. Y. Srinivasan
2015-12-11  0:14     ` K. Y. Srinivasan
2015-12-11  9:12     ` Johannes Thumshirn
2015-12-11  9:12       ` Johannes Thumshirn
2015-12-11  8:47   ` [PATCH 1/4] scsi: storvsc: Fix a bug in the layout of the hv_fc_wwn_packet Johannes Thumshirn
2015-12-12  3:10     ` KY Srinivasan
2015-12-12  3:10       ` KY Srinivasan

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=20151211102519.GF5284@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=jbottomley@parallels.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ohering@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.