All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv2] qemu-img: add special exit code if bdrv_check is not supported
Date: Thu, 24 Oct 2013 08:00:46 +0100	[thread overview]
Message-ID: <5268C59E.7060103@redhat.com> (raw)
In-Reply-To: <1382597614-8973-1-git-send-email-pl@kamp.de>

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

On 10/24/2013 07:53 AM, Peter Lieven wrote:
> currently it is not possible to distinguish by exitcode if there
> has been an error or if bdrv_check is not supported by the image
> format. Change the exitcode from 1 to 63 for the latter case.
> 
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> v1->v2: As Eric suggested changed the exitcode from 255 to 63.
> 
>  qemu-img.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Should the man page document this exit status?  Then again, it doesn't
document ANY exit status, so that could be a separate patch.

Reviewed-by: Eric Blake <eblake@redhat.com>

> 
> diff --git a/qemu-img.c b/qemu-img.c
> index 926f0a0..bf3fb4f 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -607,7 +607,7 @@ static int img_check(int argc, char **argv)
>          if (output_format == OFORMAT_HUMAN) {
>              error_report("This image format does not support checks");
>          }
> -        ret = 1;
> +        ret = 63;
>          goto fail;
>      }
>  
> 

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-10-24  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  6:53 [Qemu-devel] [PATCHv2] qemu-img: add special exit code if bdrv_check is not supported Peter Lieven
2013-10-24  7:00 ` Eric Blake [this message]
2013-10-24 10:04   ` 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=5268C59E.7060103@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --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 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.