From: Wei Liu <wei.liu2@citrix.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v1 7/7] tools/livepatch: Exit with 2 if a timeout occurs
Date: Mon, 12 Dec 2016 17:02:34 +0000 [thread overview]
Message-ID: <20161212170234.GF25175@citrix.com> (raw)
In-Reply-To: <1481559490-13844-8-git-send-email-ross.lagerwall@citrix.com>
On Mon, Dec 12, 2016 at 04:18:10PM +0000, Ross Lagerwall wrote:
> Exit with 0 for success.
> Exit with 1 for an error.
> Exit with 2 if the operation should be retried for any reason (e.g. a
> timeout or because another operation was in progress).
>
> This allows a program or script driving xen-livepatch to determine if
> the operation should be retried without parsing the output.
>
> Fix a number of incorrect uses of errno after an operation that could
> set it (e.g. fprintf, close).
This should probably be split out to another patch so that it can be
backported to 4.7 and 4.8?
> {
> @@ -485,7 +490,24 @@ int main(int argc, char *argv[])
>
> xc_interface_close(xch);
>
> - return !!ret;
> + /*
> + * Exitcode 0 for success.
> + * Exitcode 1 for an error.
> + * Exitcode 2 if the operation should be retried for any reason (e.g. a
> + * timeout or because another operation was in progress).
> + */
> +
> +#define EXIT_TIMEOUT (EXIT_FAILURE + 1)
I doubt there would be any other value used for EXIT_FAILURE, but to
make sure the code matches the comment, please:
BUILD_BUG_ON(EXIT_SUCCESS != 0);
BUILD_BUG_ON(EXIT_FAILURE != 1);
> + switch ( ret )
> + {
> + case 0:
> + return EXIT_SUCCESS;
> + case EAGAIN:
> + case EBUSY:
> + return EXIT_TIMEOUT;
> + default:
> + return EXIT_FAILURE;
> + }
> }
>
> /*
> --
> 2.7.4
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-12-12 17:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 16:18 [PATCH v1 0/7] xen-livepatch misc fixes/changes Ross Lagerwall
2016-12-12 16:18 ` [PATCH v1 1/7] tools/livepatch: Show the correct expected state before action Ross Lagerwall
2016-12-12 17:02 ` Wei Liu
2016-12-12 16:18 ` [PATCH v1 2/7] tools/livepatch: Set stdout and stderr unbuffered Ross Lagerwall
2016-12-12 17:02 ` Wei Liu
2016-12-14 6:44 ` Ross Lagerwall
2016-12-14 7:43 ` Wei Liu
2016-12-12 16:18 ` [PATCH v1 3/7] tools/livepatch: Improve output Ross Lagerwall
2016-12-12 17:02 ` Wei Liu
2016-12-12 17:11 ` Konrad Rzeszutek Wilk
2016-12-12 16:18 ` [PATCH v1 4/7] livepatch: Set timeout unit to nanoseconds Ross Lagerwall
2016-12-12 17:02 ` Wei Liu
2016-12-12 17:13 ` Konrad Rzeszutek Wilk
2016-12-12 16:18 ` [PATCH v1 5/7] tools/livepatch: Remove pointless retry loop Ross Lagerwall
2016-12-12 17:03 ` Wei Liu
2016-12-12 16:18 ` [PATCH v1 6/7] tools/livepatch: Remove unused struct member Ross Lagerwall
2016-12-12 17:03 ` Wei Liu
2016-12-12 17:13 ` Konrad Rzeszutek Wilk
2016-12-12 16:18 ` [PATCH v1 7/7] tools/livepatch: Exit with 2 if a timeout occurs Ross Lagerwall
2016-12-12 17:02 ` Wei Liu [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=20161212170234.GF25175@citrix.com \
--to=wei.liu2@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=ross.lagerwall@citrix.com \
--cc=xen-devel@lists.xen.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).