From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] scsi-block: Handle error from host devices
Date: Wed, 4 Apr 2018 10:37:51 +0800 [thread overview]
Message-ID: <20180404023751.GJ6839@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180404014702.16099-1-famz@redhat.com>
On Wed, 04/04 09:47, Fam Zheng wrote:
> The callback of blk_aio_ioctl is not sensible to SCSI errors, so
> werror=stop doesn't work if ioctl returns 0 but the scsi status is
> error.
>
> Peek at the sg_io_hdr_t fields and amend ret to fix that.
>
> Signed-off-by: Fam Zheng <famz@redhat.com>
>
> ---
>
> v2: Fix ->cb. [Daniel]
> ---
> hw/scsi/scsi-disk.c | 21 ++++++++++++++++++++-
> 1 file changed, 20 insertions(+), 1 deletion(-)
>
> diff --git a/hw/scsi/scsi-disk.c b/hw/scsi/scsi-disk.c
> index f5ab767ab5..9cb08ff491 100644
> --- a/hw/scsi/scsi-disk.c
> +++ b/hw/scsi/scsi-disk.c
> @@ -2651,10 +2651,26 @@ typedef struct SCSIBlockReq {
> /* Selected bytes of the original CDB, copied into our own CDB. */
> uint8_t cmd, cdb1, group_number;
>
> + BlockCompletionFunc *cb;
> + void *cb_opaque;
> +
> /* CDB passed to SG_IO. */
> uint8_t cdb[16];
> } SCSIBlockReq;
>
> +static void scsi_block_sgio_cb(void *opaque, int ret)
> +{
> + SCSIBlockReq *req = opaque;
> +
> + if (!ret &&
> + (req->io_header.status ||
> + req->io_header.host_status ||
> + req->io_header.driver_status)) {
> + ret = -EIO;
> + }
> + req->cb(req->cb_opaque, ret);
> +}
> +
> static BlockAIOCB *scsi_block_do_sgio(SCSIBlockReq *req,
> int64_t offset, QEMUIOVector *iov,
> int direction,
> @@ -2734,7 +2750,10 @@ static BlockAIOCB *scsi_block_do_sgio(SCSIBlockReq *req,
> io_header->usr_ptr = r;
> io_header->flags |= SG_FLAG_DIRECT_IO;
>
> - aiocb = blk_aio_ioctl(s->qdev.conf.blk, SG_IO, io_header, cb, opaque);
> + req->cb = cb;
> + req->cb_opaque = opaque;
> + aiocb = blk_aio_ioctl(s->qdev.conf.blk, SG_IO, io_header,
> + scsi_block_sgio_cb, req);
> assert(aiocb != NULL);
> return aiocb;
> }
> --
> 2.14.3
>
Hmm, now I see scsi_block_dma_command sets
r->req.status = &r->io_header.status;
and scsi_disk_req_check_error already looks at the SCSI status code. Maybe
this patch is not necessary, I'll check.
Fam
prev parent reply other threads:[~2018-04-04 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 1:47 [Qemu-devel] [PATCH v2] scsi-block: Handle error from host devices Fam Zheng
2018-04-04 2:37 ` Fam Zheng [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=20180404023751.GJ6839@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=danielhb@linux.vnet.ibm.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 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).