All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2][linux 2.6.18] scsiback: free resources after error
Date: Fri, 04 Jul 2014 12:02:46 +0200	[thread overview]
Message-ID: <53B67BC6.70108@suse.com> (raw)
In-Reply-To: <53B692BD02000078000209B8@mail.emea.novell.com>

On 07/04/2014 11:40 AM, Jan Beulich wrote:
> From: Juergen Gross <jgross@suse.com>
>
> In case of an error during preparing an I/O the already allocated resources
> should all be freed again and the frontend request should be terminated
> accordingly.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
>
> Some formatting adjustments to the changes above, and some more releasing
> of resources (in the VSCSIIF_ACT_SCSI_RESET and default cases of the switch
> in scsiback_do_cmd_fn()).

For your additional changes:

Reviewed-by: Juergen Gross <jgross@suse.com>

>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/drivers/xen/scsiback/common.h
> +++ b/drivers/xen/scsiback/common.h
> @@ -163,13 +163,13 @@ struct scsi_device *scsiback_do_translat
>   void scsiback_release_translation_entry(struct vscsibk_info *info);
>
>
> -void scsiback_cmd_exec(pending_req_t *pending_req);
> +int scsiback_cmd_exec(pending_req_t *pending_req);
>   void scsiback_do_resp_with_sense(char *sense_buffer, int32_t result,
>   			uint32_t resid, pending_req_t *pending_req);
>   void scsiback_fast_flush_area(pending_req_t *req);
>
>   void scsiback_rsp_emulation(pending_req_t *pending_req);
> -void scsiback_req_emulation_or_cmdexec(pending_req_t *pending_req);
> +int scsiback_req_emulation_or_cmdexec(pending_req_t *pending_req);
>   void scsiback_emulation_init(void);
>
>
> --- a/drivers/xen/scsiback/emulate.c
> +++ b/drivers/xen/scsiback/emulate.c
> @@ -345,16 +345,16 @@ void scsiback_rsp_emulation(pending_req_
>   }
>
>
> -void scsiback_req_emulation_or_cmdexec(pending_req_t *pending_req)
> +int scsiback_req_emulation_or_cmdexec(pending_req_t *pending_req)
>   {
> -	if (__pre_do_emulation(pending_req, NULL)) {
> -		scsiback_cmd_exec(pending_req);
> -	}
> -	else {
> -		scsiback_fast_flush_area(pending_req);
> -		scsiback_do_resp_with_sense(pending_req->sense_buffer,
> -		  pending_req->rslt, pending_req->resid, pending_req);
> -	}
> +	if (__pre_do_emulation(pending_req, NULL))
> +		return scsiback_cmd_exec(pending_req);
> +
> +	scsiback_fast_flush_area(pending_req);
> +	scsiback_do_resp_with_sense(pending_req->sense_buffer,
> +				    pending_req->rslt, pending_req->resid,
> +				    pending_req);
> +	return 0;
>   }
>
>
> --- a/drivers/xen/scsiback/scsiback.c
> +++ b/drivers/xen/scsiback/scsiback.c
> @@ -429,14 +429,14 @@ free_bios:
>   }
>
>
> -void scsiback_cmd_exec(pending_req_t *pending_req)
> +int scsiback_cmd_exec(pending_req_t *pending_req)
>   {
>   	int cmd_len  = (int)pending_req->cmd_len;
>   	int data_dir = (int)pending_req->sc_data_direction;
>   	unsigned int nr_segments = (unsigned int)pending_req->nr_segments;
>   	unsigned int timeout;
>   	struct request *rq;
> -	int write;
> +	int write, err;
>
>   	DPRINTK("%s\n",__FUNCTION__);
>
> @@ -463,17 +463,19 @@ void scsiback_cmd_exec(pending_req_t *pe
>   	rq->end_io_data = pending_req;
>
>   	if (nr_segments) {
> -
> -		if (request_map_sg(rq, pending_req, nr_segments)) {
> -			printk(KERN_ERR "scsiback: SG Request Map Error\n");
> -			return;
> +		err = request_map_sg(rq, pending_req, nr_segments);
> +		if (err) {
> +			printk(KERN_ERR "scsiback: SG Request Map error %d\n",
> +			       err);
> +			blk_put_request(rq);
> +			return err;
>   		}
>   	}
>
>   	scsiback_get(pending_req->info);
>   	blk_execute_rq_nowait(rq->q, NULL, rq, 1, scsiback_cmd_done);
>
> -	return ;
> +	return 0;
>   }
>
>
> @@ -615,17 +617,28 @@ static int scsiback_do_cmd_fn(struct vsc
>   		switch (err ?: pending_req->act) {
>   		case VSCSIIF_ACT_SCSI_CDB:
>   			/* The Host mode is through as for Emulation. */
> -			if (info->feature == VSCSI_TYPE_HOST)
> -				scsiback_cmd_exec(pending_req);
> -			else
> -				scsiback_req_emulation_or_cmdexec(pending_req);
> +			if (info->feature == VSCSI_TYPE_HOST ?
> +			    scsiback_cmd_exec(pending_req) :
> +			    scsiback_req_emulation_or_cmdexec(pending_req)) {
> +				scsiback_fast_flush_area(pending_req);
> +				scsiback_do_resp_with_sense(NULL,
> +							    DRIVER_ERROR << 24,
> +							    0, pending_req);
> +			}
>   			break;
>   		case VSCSIIF_ACT_SCSI_RESET:
> +			/* Just for pointlessly specified segments: */
> +			scsiback_fast_flush_area(pending_req);
>   			scsiback_device_reset_exec(pending_req);
>   			break;
>   		default:
> -			if(!err && printk_ratelimit())
> -				printk(KERN_ERR "scsiback: invalid request\n");
> +			if(!err) {
> +				scsiback_fast_flush_area(pending_req);
> +				if (printk_ratelimit())
> +					printk(KERN_ERR
> +					       "scsiback: invalid request %#x\n",
> +					       pending_req->act);
> +			}
>   			scsiback_do_resp_with_sense(NULL, DRIVER_ERROR << 24,
>   						    0, pending_req);
>   			break;
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
>

      reply	other threads:[~2014-07-04 10:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  4:41 [PATCH][linux 2.6.18] scsiback: free resources after error jgross
2014-07-04  9:40 ` [PATCH v2][linux " Jan Beulich
2014-07-04 10:02   ` Juergen Gross [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=53B67BC6.70108@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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 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.