summaryrefslogtreecommitdiff
path: root/sys/src/cmd/5e
diff options
context:
space:
mode:
authorcinap_lenrek <cinap_lenrek@felloff.net>2020-05-02 17:32:01 +0200
committercinap_lenrek <cinap_lenrek@felloff.net>2020-05-02 17:32:01 +0200
commitac88ce4f7f19be1aae1fdf390fa870b4be8dc3f5 (patch)
tree47df6acf41dd8d2dc607b89af9d4667935d0c952 /sys/src/cmd/5e
parent7ff6ea0f70307d4b82e6df69eb1310a6e27aa4ad (diff)
make bind(2) error handling consistent
The mount() and bind() syscalls return -1 on error, and the mountid sequence number on success. The manpage states that the mountid sequence number is a positive integer, but the kernels implementation currently uses a unsigned 32-bit integer and does not guarantee that the mountid will not become negative. Most code just cares about the error, so test for the -1 error value only.
Diffstat (limited to 'sys/src/cmd/5e')
-rw-r--r--sys/src/cmd/5e/5e.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/src/cmd/5e/5e.c b/sys/src/cmd/5e/5e.c
index 85367c3ee..b91a083ea 100644
--- a/sys/src/cmd/5e/5e.c
+++ b/sys/src/cmd/5e/5e.c
@@ -23,9 +23,9 @@ dump(void)
static void
adjustns(void)
{
- if(bind("/arm/bin", "/bin", MREPL) < 0)
+ if(bind("/arm/bin", "/bin", MREPL) == -1)
sysfatal("bind: %r");
- if(bind("/rc/bin", "/bin", MAFTER) < 0)
+ if(bind("/rc/bin", "/bin", MAFTER) == -1)
sysfatal("bind: %r");
putenv("cputype", "arm");
putenv("objtype", "arm");