diff options
| author | Rich Felker <dalias@aerifal.cx> | 2020-09-03 17:37:11 -0400 |
|---|---|---|
| committer | Rich Felker <dalias@aerifal.cx> | 2020-09-03 17:37:11 -0400 |
| commit | b8b729bd22c28c9116c2fce65dce207a35299c26 (patch) | |
| tree | 8a44d7f01cd53d1e03a8345a82b3b784de3f8091 /crt/sh/crti.s | |
| parent | 262003ad9d8894c03fa4b033140e1e14e4c24c4d (diff) | |
| download | musl-b8b729bd22c28c9116c2fce65dce207a35299c26.tar.gz musl-b8b729bd22c28c9116c2fce65dce207a35299c26.tar.bz2 musl-b8b729bd22c28c9116c2fce65dce207a35299c26.tar.xz musl-b8b729bd22c28c9116c2fce65dce207a35299c26.zip | |
fix missing O_LARGEFILE values on x86_64, x32, and mips64
prior to commit 685e40bb09f5f24a2af54ea09c97328808f76990, x86_64 was
correctly passing O_LARGEFILE to SYS_open; it was removed (defined to
0 in the public header, and changed to use the public definition) as
part of that change, probably out of a mistaken belief that it's not
needed.
however, on a mixed system with 32-bit and 64-bit binaries, it's
important that all files be opened with O_LARGEFILE, even if the
opening process is 64-bit, in case a descriptor is passed to a 32-bit
process. otherwise, attempts to access past 2GB in the 32-bit process
could produce EOVERFLOW.
most 64-bit archs added later got this right alread, except for
mips64. x32 was also affected. there are now fixed.
Diffstat (limited to 'crt/sh/crti.s')
0 files changed, 0 insertions, 0 deletions