qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Niels de Vos <ndevos@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.6 1/2] block/gluster: return correct error value
Date: Wed, 6 Apr 2016 17:00:49 +0200	[thread overview]
Message-ID: <20160406150049.GN17260@ndevos-x240.usersys.redhat.com> (raw)
In-Reply-To: <a88fcaed20c098f116116ec6d38e5e7cc5326c4e.1459913103.git.jcody@redhat.com>

On Tue, Apr 05, 2016 at 11:29:51PM -0400, Jeff Cody wrote:
> Upon error, gluster will call the aio callback function with a
> ret value of -1, with errno set to the proper error value.  If
> we set the acb->ret value to the return value in the callback,
> that results in every error being EPERM (i.e. 1).  Instead, set
> it to the proper error result.
> 
> Signed-off-by: Jeff Cody <jcody@redhat.com>

Looks good to me.

Reviewed-by: Niels de Vos <ndevos@redhat.com>

> ---
>  block/gluster.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/block/gluster.c b/block/gluster.c
> index 7bface2..30a827e 100644
> --- a/block/gluster.c
> +++ b/block/gluster.c
> @@ -245,7 +245,7 @@ static void gluster_finish_aiocb(struct glfs_fd *fd, ssize_t ret, void *arg)
>      if (!ret || ret == acb->size) {
>          acb->ret = 0; /* Success */
>      } else if (ret < 0) {
> -        acb->ret = ret; /* Read/Write failed */
> +        acb->ret = -errno; /* Read/Write failed */
>      } else {
>          acb->ret = -EIO; /* Partial read/write - fail it */
>      }
> -- 
> 1.9.3
> 

  reply	other threads:[~2016-04-06 15:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  3:29 [Qemu-devel] [PATCH for-2.6 0/2] Bug fixes for gluster Jeff Cody
2016-04-06  3:29 ` [Qemu-devel] [PATCH for-2.6 1/2] block/gluster: return correct error value Jeff Cody
2016-04-06 15:00   ` Niels de Vos [this message]
2016-04-06  3:29 ` [Qemu-devel] [PATCH for-2.6 2/2] block/gluster: prevent data loss after i/o error Jeff Cody
2016-04-06 11:02   ` Kevin Wolf
2016-04-06 11:19     ` Ric Wheeler
2016-04-06 11:41       ` Kevin Wolf
2016-04-06 11:51         ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-04-06 13:10           ` Jeff Cody
2016-04-06 13:20             ` Kevin Wolf
2016-04-07  7:48               ` Pranith Kumar Karampuri
2016-04-11  4:26                 ` Raghavendra Gowdappa
2016-05-09  6:38                   ` Raghavendra Talur
2016-05-09  8:02                     ` Kevin Wolf
2016-04-06 12:44     ` [Qemu-devel] " Jeff Cody
2016-04-06 14:47       ` Niels de Vos
2016-04-06 16:05         ` Jeff Cody
2016-04-07 16:17     ` Jeff Cody

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=20160406150049.GN17260@ndevos-x240.usersys.redhat.com \
    --to=ndevos@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).