cinap_lenrek ac88ce4f7f 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.		2020-05-02 17:32:01 +02:00
..
5e.c	make bind(2) error handling consistent	2020-05-02 17:32:01 +02:00
arm.c	5e: byte access incorrectly checked for long; brk has to round up addresses	2018-09-28 22:53:24 +00:00
dat.h
fns.h
fpa.c
fs.c
mkfile
proc.c
seg.c
sys.c	5e: byte access incorrectly checked for long; brk has to round up addresses	2018-09-28 22:53:24 +00:00
util.c
vfp.c