diff options
| author | Sergey Bugaev <bugaevc@gmail.com> | 2024-12-04 14:29:15 +0300 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2024-12-05 08:49:35 +0100 |
| commit | 8cbab3b729a6a2335aeafb34d55d758c7062f2d8 (patch) | |
| tree | 8c351367a8f2a8790e13a6de8f79217a74f4def7 /scripts/tst-elf-edit.py | |
| parent | 00de38e531f55ca095910e655a0666ccb33fb6f6 (diff) | |
| download | glibc-8cbab3b729a6a2335aeafb34d55d758c7062f2d8.zip glibc-8cbab3b729a6a2335aeafb34d55d758c7062f2d8.tar.gz glibc-8cbab3b729a6a2335aeafb34d55d758c7062f2d8.tar.bz2 | |
hurd: Protect against servers returning bogus read/write lengths
There already was a branch checking for this case in _hurd_fd_read ()
when the data is returned out-of-line. Do the same for inline data, as
well as for _hurd_fd_write (). It's also not possible for the length to
be negative, since it's stored in an unsigned integer.
Not verifying the returned length can confuse the callers who assume
the returned length is always reasonable. This manifested as libzstd
test suite failing on writes to /dev/zero, even though the write () call
appeared to succeed. In fact, the zero store backing /dev/zero was
returning a larger written length than the size actually submitted to
it, which is a separate bug to be fixed on the Hurd side. With this
patch, EGRATUITOUS is now propagated to the caller.
Reported-by: Diego Nieto Cid <dnietoc@gmail.com>
Signed-off-by: Sergey Bugaev <bugaevc@gmail.com>
Message-ID: <20241204112915.540032-1-bugaevc@gmail.com>
Diffstat (limited to 'scripts/tst-elf-edit.py')
0 files changed, 0 insertions, 0 deletions