diff options
| author | cinap_lenrek <cinap_lenrek@felloff.net> | 2020-05-02 17:32:01 +0200 |
|---|---|---|
| committer | cinap_lenrek <cinap_lenrek@felloff.net> | 2020-05-02 17:32:01 +0200 |
| commit | ac88ce4f7f19be1aae1fdf390fa870b4be8dc3f5 (patch) | |
| tree | 47df6acf41dd8d2dc607b89af9d4667935d0c952 /sys/src/cmd/bzfs | |
| parent | 7ff6ea0f70307d4b82e6df69eb1310a6e27aa4ad (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/bzfs')
| -rw-r--r-- | sys/src/cmd/bzfs/oramfs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/src/cmd/bzfs/oramfs.c b/sys/src/cmd/bzfs/oramfs.c index e5d7ad0a2..27b5f8410 100644 --- a/sys/src/cmd/bzfs/oramfs.c +++ b/sys/src/cmd/bzfs/oramfs.c @@ -208,7 +208,7 @@ ramfsmain(int argc, char *argv[]) break; default: close(mfd[0]); /* don't deadlock if child fails */ - if(defmnt && mount(srvfd, -1, defmnt, MREPL|MCREATE, "") < 0) + if(defmnt && mount(srvfd, -1, defmnt, MREPL|MCREATE, "") == -1) error("mount failed: %r"); } } |