https://bugs.kde.org/show_bug.cgi?id=381304
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=381304
--- Comment #5 from John Reiser ---
(In reply to John Reiser from comment #3)
> There is no guarantee that the kernel avoids writing into any
> portion of the whole buffer, although all known implementations write only
> an initial string [non-terminate
https://bugs.kde.org/show_bug.cgi?id=381304
--- Comment #4 from John Reiser ---
read_length = read(fd, buf, buflen) should regard buf[read_length, buflen) as
Uninit when there is no error. When there is an error, then ALL of buf[0,
buflen) should be regarded as Uninit. This is particularly true
https://bugs.kde.org/show_bug.cgi?id=381304
--- Comment #3 from John Reiser ---
Another syscall that produces uninit is readlink(). The portion of the result
buffer that is beyond the returned length, should be regarded as Uninit. There
is no guarantee that the kernel avoids writing into any po
https://bugs.kde.org/show_bug.cgi?id=381304
--- Comment #2 from John Reiser ---
The system routines in musl libc (https://www.musl-libc.org/) are coded with
the system call instruction as a common tail.
The system call which produces uninit values is brk()/sbrk(), which libmusl
invokes from mall
https://bugs.kde.org/show_bug.cgi?id=381304
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet.
