From: Hu Tao <hutao@cn.fujitsu.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [PATCH v3 2/2] virtio-scsi: add error handling
Date: Sat, 10 Mar 2012 16:48:07 +0800 [thread overview]
Message-ID: <20120310084806.GB24958@localhost.localdomain> (raw)
In-Reply-To: <1324296188-3426-3-git-send-email-pbonzini@redhat.com>
On Mon, Dec 19, 2011 at 01:03:08PM +0100, Paolo Bonzini wrote:
> -/* These are still stubs. */
> static void virtscsi_complete_free(void *buf)
> {
> struct virtio_scsi_cmd *cmd = buf;
>
> + if (cmd->comp)
> + complete_all(cmd->comp);
> mempool_free(cmd, virtscsi_cmd_pool);
> }
>
> @@ -306,12 +308,79 @@ out:
> return ret;
> }
>
> +static int virtscsi_tmf(struct virtio_scsi *vscsi, struct virtio_scsi_cmd *cmd)
> +{
> + DECLARE_COMPLETION_ONSTACK(comp);
> + int ret;
> +
> + cmd->comp = ∁
> + ret = virtscsi_kick_cmd(vscsi, vscsi->ctrl_vq, cmd);
> + if (ret < 0)
> + return FAILED;
> +
> + wait_for_completion(&comp);
> + if (cmd->resp.tmf.response != VIRTIO_SCSI_S_OK &&
> + cmd->resp.tmf.response != VIRTIO_SCSI_S_FUNCTION_SUCCEEDED)
> + return FAILED;
Is there a race here that the cmd may have been already freed (by
virtscsi_complete_free) after waking up from the completion?
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
index 3f20678..7cba05d 100644
--- a/drivers/scsi/virtio_scsi.c
+++ b/drivers/scsi/virtio_scsi.c
@@ -175,7 +175,8 @@ static void virtscsi_complete_free(void *buf)
if (cmd->comp)
complete_all(cmd->comp);
- mempool_free(cmd, virtscsi_cmd_pool);
+ else
+ mempool_free(cmd, virtscsi_cmd_pool);
}
static void virtscsi_ctrl_done(struct virtqueue *vq)
@@ -305,7 +306,7 @@ out:
static int virtscsi_tmf(struct virtio_scsi *vscsi, struct virtio_scsi_cmd *cmd)
{
DECLARE_COMPLETION_ONSTACK(comp);
- int ret;
+ int ret = SUCCESS;
cmd->comp = ∁
ret = virtscsi_kick_cmd(vscsi, vscsi->ctrl_vq, cmd);
@@ -315,9 +316,10 @@ static int virtscsi_tmf(struct virtio_scsi *vscsi, struct virtio_scsi_cmd *cmd)
wait_for_completion(&comp);
if (cmd->resp.tmf.response != VIRTIO_SCSI_S_OK &&
cmd->resp.tmf.response != VIRTIO_SCSI_S_FUNCTION_SUCCEEDED)
- return FAILED;
+ ret = FAILED;
- return SUCCESS;
+ mempool_free(cmd, virtscsi_cmd_pool);
+ return ret;
}
static int virtscsi_device_reset(struct scsi_cmnd *sc)
> +
> + return SUCCESS;
> +}
--
Thanks,
Hu Tao
next prev parent reply other threads:[~2012-03-11 4:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 12:03 [PATCH v3 0/2] virtio-scsi driver Paolo Bonzini
2011-12-19 12:03 ` [PATCH v3 1/2] virtio-scsi: first version Paolo Bonzini
2011-12-19 12:22 ` Hannes Reinecke
2011-12-19 13:11 ` Paolo Bonzini
2011-12-19 15:00 ` Douglas Gilbert
2011-12-19 15:17 ` Paolo Bonzini
2011-12-19 14:17 ` Douglas Gilbert
2011-12-19 12:03 ` [PATCH v3 2/2] virtio-scsi: add error handling Paolo Bonzini
2012-03-10 8:48 ` Hu Tao [this message]
2012-03-11 12:47 ` Paolo Bonzini
2012-03-14 6:35 ` Hu Tao
2012-03-10 7:34 ` [PATCH v3 0/2] virtio-scsi driver Hu Tao
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=20120310084806.GB24958@localhost.localdomain \
--to=hutao@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox