From: Luiz Capitulino <lcapitulino@redhat.com>
To: linux-rt-users@vger.kernel.org
Cc: williams@redhat.com, jkacur@redhat.com
Subject: [PATCH 2/3] don't use exit(-1) for failures
Date: Thu, 17 Mar 2016 14:29:04 -0400 [thread overview]
Message-ID: <1458239345-30892-3-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1458239345-30892-1-git-send-email-lcapitulino@redhat.com>
The kernel uses only 8 bits of the status as a return
code, so this actually becomes 255 in the shell.
In any case, the most widely convension is exit(1)
for failures, so let's be consistent.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
src/pi_tests/pi_stress.c | 2 +-
src/pi_tests/pip_stress.c | 6 +++---
src/rt-migrate-test/rt-migrate-test.c | 5 ++---
src/signaltest/signaltest.c | 2 +-
4 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/src/pi_tests/pi_stress.c b/src/pi_tests/pi_stress.c
index a02f706..36b64ca 100644
--- a/src/pi_tests/pi_stress.c
+++ b/src/pi_tests/pi_stress.c
@@ -634,7 +634,7 @@ int verify_cpu(int cpu)
if (status == -1) {
err = errno;
fprintf(stderr, "sched_getaffinity %s\n", strerror(err));
- exit(-1);
+ exit(1);
}
if (CPU_ISSET(cpu, &mask))
diff --git a/src/pi_tests/pip_stress.c b/src/pi_tests/pip_stress.c
index a0477cc..e6cf0ce 100644
--- a/src/pi_tests/pip_stress.c
+++ b/src/pi_tests/pip_stress.c
@@ -95,7 +95,7 @@ int main(void)
*minimum_priority = sched_get_priority_min(policy);
if (check_privs())
- exit(-1);
+ exit(1);
mptr = mmap_page(); /* Get a page of shared memory */
resource = (pthread_mutex_t*)mptr; /* point our lock to it */
@@ -138,7 +138,7 @@ int main(void)
pid2 = fork(); /* parent code */
if (pid2 == -1) {
perror("fork: ");
- exit(-1);
+ exit(1);
} else if (pid2 != 0) { /* parent code */
high(pid2);
} else { /* child code */
@@ -231,7 +231,7 @@ void *mmap_page(void)
mptr = mmap(NULL, pgsize, PROTRW, MMAP_FLAGS, 0, 0);
if (mptr == MAP_FAILED) {
perror("In function mmap_page - mmap");
- exit(-1);
+ exit(1);
}
return mptr;
diff --git a/src/rt-migrate-test/rt-migrate-test.c b/src/rt-migrate-test/rt-migrate-test.c
index 1362404..a00e86f 100644
--- a/src/rt-migrate-test/rt-migrate-test.c
+++ b/src/rt-migrate-test/rt-migrate-test.c
@@ -138,7 +138,7 @@ static void perr(char *fmt, ...)
perror(buffer);
fflush(stderr);
- exit(-1);
+ exit(1);
}
static void print_progress_bar(int percent)
@@ -226,7 +226,6 @@ static void parse_options (int argc, char *argv[])
break;
}
}
-
}
static unsigned long long get_time(void)
@@ -604,7 +603,7 @@ int main (int argc, char **argv)
exit(2);
}
if (check < 0)
- exit(-1);
+ exit(1);
else
exit(0);
diff --git a/src/signaltest/signaltest.c b/src/signaltest/signaltest.c
index b80969b..59f979e 100644
--- a/src/signaltest/signaltest.c
+++ b/src/signaltest/signaltest.c
@@ -323,7 +323,7 @@ int main(int argc, char **argv)
process_options(argc, argv);
if (check_privs())
- exit(-1);
+ exit(1);
/* lock all memory (prevent paging) */
if (lockall)
--
2.1.0
next prev parent reply other threads:[~2016-03-17 18:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 18:29 [PATCH v2 0/3] rt-tests: minor fixes Luiz Capitulino
2016-03-17 18:29 ` [PATCH 1/3] rt-migrate-test: fix return code Luiz Capitulino
2016-03-22 14:22 ` John Kacur
2016-03-22 14:47 ` Luiz Capitulino
2016-03-22 14:59 ` John Kacur
2016-03-22 15:30 ` Luiz Capitulino
2016-03-22 16:24 ` John Kacur
2016-03-22 16:43 ` Luiz Capitulino
2016-03-22 15:05 ` John Kacur
2016-03-17 18:29 ` Luiz Capitulino [this message]
2016-03-22 14:21 ` [PATCH 2/3] don't use exit(-1) for failures John Kacur
2016-03-22 14:30 ` Luiz Capitulino
2016-04-14 6:53 ` Uwe Kleine-König
2016-03-17 18:29 ` [PATCH 3/3] cyclictest: initialize 'stop' early Luiz Capitulino
2016-03-22 14:55 ` John Kacur
2016-03-22 14:59 ` Luiz Capitulino
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=1458239345-30892-3-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@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).