From: Hannes Reinecke <hare@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Jim Minter <jminter@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] sda abort with virtio-scsi
Date: Thu, 4 Feb 2016 16:11:07 +0100 [thread overview]
Message-ID: <56B36A0B.8070605@suse.de> (raw)
In-Reply-To: <56B36852.8000101@redhat.com>
On 02/04/2016 04:03 PM, Paolo Bonzini wrote:
>> diff --git a/drivers/scsi/virtio_scsi.c b/drivers/scsi/virtio_scsi.c
>> index 595af1a..f712db5 100644
>> --- a/drivers/scsi/virtio_scsi.c
>> +++ b/drivers/scsi/virtio_scsi.c
>> @@ -543,6 +543,33 @@ static int virtscsi_abort(struct scsi_cmnd *sc)
>> return virtscsi_tmf(vscsi, cmd);
>> }
>>
>> +static enum blk_eh_timer_return virtscsi_timed_out(struct scsi_cmnd *sc)
>> +{
>> + struct virtio_scsi *vscsi = shost_priv(sc->device->host);
>> + struct virtio_scsi_cmd *cmd;
>> +
>> + scmd_printk(KERN_INFO, sc, "timeout\n");
>> + cmd = mempool_alloc(virtscsi_cmd_pool, GFP_NOIO);
>> + if (!cmd)
>> + return FAILED;
>
> Should this be BLK_EH_NOT_HANDLED? Apart from this, the patch looks
> good. And of course this doesn't affect Jim, who can test this patch
> anyway.
>
Why, but of course.
I'll be sending the official patch to linux-scsi.
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-02-04 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:46 [Qemu-devel] sda abort with virtio-scsi Jim Minter
2016-02-03 23:19 ` Paolo Bonzini
2016-02-03 23:34 ` Jim Minter
2016-02-04 10:23 ` Paolo Bonzini
2016-02-04 11:00 ` Denis V. Lunev
2016-02-04 13:41 ` Jim Minter
2016-02-04 13:54 ` Hannes Reinecke
2016-02-04 15:03 ` Paolo Bonzini
2016-02-04 15:11 ` Hannes Reinecke [this message]
2016-02-08 20:02 ` Jim Minter
2016-02-04 6:59 ` Hannes Reinecke
2016-02-04 11:27 ` Paolo Bonzini
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=56B36A0B.8070605@suse.de \
--to=hare@suse.de \
--cc=jminter@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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.