qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Pavel Borzenkov <pborzenkov@virtuozzo.com>,
	Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] block: fix return code for partial write for Linux AIO
Date: Tue, 28 Jun 2016 14:21:20 +0300	[thread overview]
Message-ID: <57725DB0.50503@openvz.org> (raw)
In-Reply-To: <1466681836-1123-1-git-send-email-den@openvz.org>

On 06/23/2016 02:37 PM, Denis V. Lunev wrote:
> Partial write most likely means that there is not space rather than
> "something wrong happens". Thus it would be more natural to return
> ENOSPC rather than EINVAL.
>
> The problem actually happens with NBD server, which has reported EINVAL
> rather then ENOSPC on the first error using its protocol, which makes
> report to the user wrong.
>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Pavel Borzenkov <pborzenkov@virtuozzo.com>
> CC: Kevin Wolf <kwolf@redhat.com>
> CC: Max Reitz <mreitz@redhat.com>
> ---
>   block/linux-aio.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/linux-aio.c b/block/linux-aio.c
> index e468960..7df8651 100644
> --- a/block/linux-aio.c
> +++ b/block/linux-aio.c
> @@ -87,7 +87,7 @@ static void qemu_laio_process_completion(struct qemu_laiocb *laiocb)
>                   qemu_iovec_memset(laiocb->qiov, ret, 0,
>                       laiocb->qiov->size - ret);
>               } else {
> -                ret = -EINVAL;
> +                ret = -ENOSPC;
>               }
>           }
>       }
ping

  reply	other threads:[~2016-06-28 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 11:37 [Qemu-devel] [PATCH 1/1] block: fix return code for partial write for Linux AIO Denis V. Lunev
2016-06-28 11:21 ` Denis V. Lunev [this message]
2016-06-28 14:22   ` Eric Blake
2016-06-28 14:37     ` Denis V. Lunev
2016-06-28 11:52 ` Kevin Wolf

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=57725DB0.50503@openvz.org \
    --to=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pborzenkov@virtuozzo.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).