diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2019-06-18 14:09:09 -0300 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2019-07-10 16:52:50 -0300 |
| commit | a008c76b56e4f958cf5a0d6f67d29fade89421b7 (patch) | |
| tree | c3f73587250f781b2c298d10762b14e09032b6b3 /nptl | |
| parent | 99135114ba23c3110b7e4e650fabdc5e639746b7 (diff) | |
| download | glibc-a008c76b56e4f958cf5a0d6f67d29fade89421b7.zip glibc-a008c76b56e4f958cf5a0d6f67d29fade89421b7.tar.gz glibc-a008c76b56e4f958cf5a0d6f67d29fade89421b7.tar.bz2 | |
posix: Fix large mmap64 offset for mips64n32 (BZ#24699)
The fix for BZ#21270 (commit 158d5fa0e19) added a mask to avoid offset larger
than 1^44 to be used along __NR_mmap2. However mips64n32 users __NR_mmap,
as mips64n64, but still defines off_t as old non-LFS type (other ILP32, such
x32, defines off_t being equal to off64_t). This leads to use the same
mask meant only for __NR_mmap2 call for __NR_mmap, thus limiting the maximum
offset it can use with mmap64.
This patch fixes by setting the high mask only for __NR_mmap2 usage. The
posix/tst-mmap-offset.c already tests it and also fails for mips64n32. The
patch also change the test to check for an arch-specific header that defines
the maximum supported offset.
Checked on x86_64-linux-gnu, i686-linux-gnu, and I also tests tst-mmap-offset
on qemu simulated mips64 with kernel 3.2.0 kernel for both mips-linux-gnu and
mips64-n32-linux-gnu.
[BZ #24699]
* posix/tst-mmap-offset.c: Mention BZ #24699.
(do_test_bz21270): Rename to do_test_large_offset and use
mmap64_maximum_offset to check for maximum expected offset value.
* sysdeps/generic/mmap_info.h: New file.
* sysdeps/unix/sysv/linux/mips/mmap_info.h: Likewise.
* sysdeps/unix/sysv/linux/mmap64.c (MMAP_OFF_HIGH_MASK): Define iff
__NR_mmap2 is used.
Diffstat (limited to 'nptl')
0 files changed, 0 insertions, 0 deletions