about summary refs log tree commit diff
path: root/src/unistd/fchownat.c
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2018-09-16 22:42:59 -0400
committerRich Felker <dalias@aerifal.cx>2018-09-16 23:03:12 -0400
commit1f6cbdb434114139081fe65a9bafe775e9ab6c41 (patch)
treedcfb6da1075643c4f596310a83bc4e45bc1f7181 /src/unistd/fchownat.c
parent849e7603e9004fd292a93df64dd3524025f2987a (diff)
downloadmusl-1f6cbdb434114139081fe65a9bafe775e9ab6c41.tar.gz
musl-1f6cbdb434114139081fe65a9bafe775e9ab6c41.tar.xz
musl-1f6cbdb434114139081fe65a9bafe775e9ab6c41.zip
getdelim: only grow buffer when necessary, improve OOM behavior
commit b114190b29417fff6f701eea3a3b3b6030338280 introduced spurious
realloc of the output buffer in cases where the result would exactly
fit in the caller-provided buffer. this is contrary to a strict
reading of the spec, which only allows realloc when the provided
buffer is "of insufficient size".

revert the adjustment of the realloc threshold, and instead push the
byte read by getc_unlocked (for which the adjustment was made) back
into the stdio buffer if it does not fit in the output buffer, to be
read in the next loop iteration.

in order not to leave a pushed-back byte in the stdio buffer if
realloc fails (which would violate the invariant that logical FILE
position and underlying open file description offset match for
unbuffered FILEs), the OOM code path must be changed. it would suffice
move just one byte in this case, but from a QoI perspective, in the
event of ENOMEM the entire output buffer (up to the allocated length
reported via *n) should contain bytes read from the FILE stream.
otherwise the caller has no way to distinguish trunated data from
uninitialized buffer space.

the SIZE_MAX/2 check is removed since the sum of disjoint object sizes
is assumed not to be able to overflow, leaving just one OOM code path.
Diffstat (limited to 'src/unistd/fchownat.c')
0 files changed, 0 insertions, 0 deletions