[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EDDAA5C.2050809@cs.wisc.edu>
Date: Mon, 05 Dec 2011 23:38:36 -0600
From: Mike Christie <michaelc@...wisc.edu>
To: Paolo Bonzini <pbonzini@...hat.com>
CC: linux-kernel@...r.kernel.org,
"Michael S. Tsirkin" <mst@...hat.com>,
linux-scsi <linux-scsi@...r.kernel.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Stefan Hajnoczi <stefanha@...ux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] virtio-scsi: add error handling
On 12/05/2011 11:29 AM, Paolo Bonzini wrote:
> +static int virtscsi_device_reset(struct scsi_cmnd *sc)
> +{
> + struct virtio_scsi *vscsi = shost_priv(sc->device->host);
> + struct virtio_scsi_cmd *cmd;
> +
> + sdev_printk(KERN_INFO, sc->device, "device reset\n");
> + cmd = kmem_cache_zalloc(virtscsi_cmd_cache, GFP_ATOMIC);
Here and in abort you can use GFP_NOIO. No locks are held here and you
just want to make sure the allocation does not cause write outs.
You probably want some cmd preallocated here and in the queuecommand
path, so you can make progress even if memory is hard to come by.
Block/scsi drivers normally use mempools to do this.
> + if (!cmd)
> + return FAILED;
> +
> + cmd->sc = sc;
> + cmd->req.tmf = (struct virtio_scsi_ctrl_tmf_req){
> + .type = VIRTIO_SCSI_T_TMF,
> + .subtype = VIRTIO_SCSI_T_TMF_LOGICAL_UNIT_RESET,
> + .lun[0] = 1,
> + .lun[1] = sc->device->id,
> + .lun[2] = (sc->device->lun >> 8) | 0x40,
> + .lun[3] = sc->device->lun & 0xff,
Not sure what is going on here. Is lun[8] is supposed to be the scsi lun
value like in the scsi specs? If so you just want
int_to_scsilun(sc->device->lun, lun);
> static struct scsi_host_template virtscsi_host_template = {
> .module = THIS_MODULE,
> .name = "Virtio SCSI HBA",
> .proc_name = "virtio_scsi",
> .queuecommand = virtscsi_queuecommand,
> .this_id = -1,
> + .eh_abort_handler = virtscsi_abort,
> + .eh_device_reset_handler = virtscsi_device_reset,
>
Tabbing looks off with the rest of your code.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists