From: Hu Tao <hutao@cn.fujitsu.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Mike Christie <michaelc@cs.wisc.edu>,
Pekka Enberg <penberg@kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH v5 2/3] virtio-scsi: add error handling
Date: Mon, 19 Mar 2012 17:55:29 +0800 [thread overview]
Message-ID: <20120319095529.GA25623@localhost.localdomain> (raw)
In-Reply-To: <1328440562-19425-3-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2214 bytes --]
On Sun, Feb 05, 2012 at 12:16:01PM +0100, Paolo Bonzini wrote:
> This commit adds basic error handling to the virtio-scsi
> HBA device. Task management functions are sent synchronously
> via the control virtqueue.
>
> Cc: linux-scsi <linux-scsi@vger.kernel.org>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Cc: kvm@vger.kernel.org
> Acked-by: Pekka Enberg <penberg@kernel.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> v3->v4: fixed 32-bit compilation; adjusted call to virtscsi_kick_cmd
>
> v2->v3: added mempool, used GFP_NOIO instead of GFP_ATOMIC,
> formatting fixes
>
> v1->v2: use scmd_printk
>
> drivers/scsi/virtio_scsi.c | 73 +++++++++++++++++++++++++++++++++++++++++++-
> 1 files changed, 72 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
> index 3f87ae0..68104cd 100644
> --- a/drivers/scsi/virtio_scsi.c
> +++ b/drivers/scsi/virtio_scsi.c
> @@ -29,6 +29,7 @@
> /* Command queue element */
> struct virtio_scsi_cmd {
> struct scsi_cmnd *sc;
> + struct completion *comp;
> union {
> struct virtio_scsi_cmd_req cmd;
> struct virtio_scsi_ctrl_tmf_req tmf;
> @@ -168,11 +169,12 @@ static void virtscsi_req_done(struct virtqueue *vq)
> virtscsi_vq_done(vq, virtscsi_complete_cmd);
> };
>
> -/* 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,81 @@ 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,
> + sizeof cmd->req.tmf, sizeof cmd->resp.tmf,
> + GFP_NOIO);
> + 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;
> +
> + return SUCCESS;
> +}
Hi Paolo,
This is against v5.
[-- Attachment #2: 0001-fix-race-in-tmf.patch --]
[-- Type: text/plain, Size: 1795 bytes --]
>From 34ef5e64fc205044e4326fcc5dcf2aa6b219763a Mon Sep 17 00:00:00 2001
From: Hu Tao <hutao@cn.fujitsu.com>
Date: Mon, 19 Mar 2012 15:58:22 +0800
Subject: [PATCH] fix two problems in tmf
This patch fix two problems in tmf:
1. race in virtscsi_tmf that the cmd may have been already freed
when waking up from the completion
2. cmd leak if virtscsi_kick_cmd fails.
Signed-off-by: Hu Tao <hutao@cn.fujitsu.com>
---
drivers/scsi/virtio_scsi.c | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
index efccd72..3b8a6e6 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)
@@ -311,21 +312,23 @@ out:
static int virtscsi_tmf(struct virtio_scsi *vscsi, struct virtio_scsi_cmd *cmd)
{
DECLARE_COMPLETION_ONSTACK(comp);
- int ret;
+ int ret = FAILED;
cmd->comp = ∁
ret = virtscsi_kick_cmd(vscsi, vscsi->ctrl_vq, cmd,
sizeof cmd->req.tmf, sizeof cmd->resp.tmf,
GFP_NOIO);
if (ret < 0)
- return FAILED;
+ goto 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;
+ if (cmd->resp.tmf.response == VIRTIO_SCSI_S_OK ||
+ cmd->resp.tmf.response == VIRTIO_SCSI_S_FUNCTION_SUCCEEDED)
+ ret = SUCCESS;
- return SUCCESS;
+failed:
+ mempool_free(cmd, virtscsi_cmd_pool);
+ return ret;
}
static int virtscsi_device_reset(struct scsi_cmnd *sc)
--
1.7.1
next prev parent reply other threads:[~2012-03-19 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 11:15 [PATCH v5 0/3] virtio-scsi driver Paolo Bonzini
2012-02-05 11:16 ` [PATCH v5 1/3] virtio-scsi: first version Paolo Bonzini
2012-02-05 11:16 ` [PATCH v5 2/3] virtio-scsi: add error handling Paolo Bonzini
2012-03-19 9:55 ` Hu Tao [this message]
2012-03-19 11:07 ` Paolo Bonzini
2012-02-05 11:16 ` [PATCH v5 3/3] virtio-scsi: add power management support Paolo Bonzini
2012-02-10 11:00 ` [PATCH v5 0/3] virtio-scsi driver Stefan Hajnoczi
2012-03-30 2:58 ` 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=20120319095529.GA25623@localhost.localdomain \
--to=hutao@cn.fujitsu.com \
--cc=kvm@vger.kernel.org \
--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=penberg@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).