From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kwolf@redhat.com, asias@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] gluster: Abort on AIO completion failure
Date: Tue, 27 Aug 2013 13:46:31 +0530 [thread overview]
Message-ID: <20130827081631.GA30031@in.ibm.com> (raw)
In-Reply-To: <521C4DFD.30805@redhat.com>
On Tue, Aug 27, 2013 at 08:58:05AM +0200, Paolo Bonzini wrote:
> > diff --git a/block/gluster.c b/block/gluster.c
> > index 46f36f8..942154a 100644
> > --- a/block/gluster.c
> > +++ b/block/gluster.c
> > @@ -427,20 +427,9 @@ static void gluster_finish_aiocb(struct glfs_fd *fd, ssize_t ret, void *arg)
> > /*
> > * Gluster AIO callback thread failed to notify the waiting
> > * QEMU thread about IO completion.
> > - *
> > - * Complete this IO request and make the disk inaccessible for
> > - * subsequent reads and writes.
> > */
> > - error_report("Gluster failed to notify QEMU about IO completion");
> > -
> > - qemu_mutex_lock_iothread(); /* We are in gluster thread context */
> > - acb->common.cb(acb->common.opaque, -EIO);
> > - qemu_aio_release(acb);
> > - close(s->fds[GLUSTER_FD_READ]);
> > - close(s->fds[GLUSTER_FD_WRITE]);
> > - qemu_aio_set_fd_handler(s->fds[GLUSTER_FD_READ], NULL, NULL, NULL);
> > - bs->drv = NULL; /* Make the disk inaccessible */
> > - qemu_mutex_unlock_iothread();
> > + error_report("Gluster AIO completion failed");
>
> Still, considering everyone can be wrong, adding the errno here is
> probably not a bad idea. :)
Sent v1 with errno added.
Regards,
Bharata.
prev parent reply other threads:[~2013-08-27 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 5:53 [Qemu-devel] [PATCH] gluster: Abort on AIO completion failure Bharata B Rao
2013-08-27 6:58 ` Paolo Bonzini
2013-08-27 8:16 ` Bharata B Rao [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=20130827081631.GA30031@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=asias@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).