diff options
| author | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-02-02 09:55:50 -0300 |
|---|---|---|
| committer | Adhemerval Zanella <adhemerval.zanella@linaro.org> | 2021-02-02 11:20:42 -0300 |
| commit | 913201078502ad3f10043db02a8efce5d75387c2 (patch) | |
| tree | 09b33f575aa30ff8a81024fae57830f6c37f5370 /sysdeps/hppa/dl-symaddr.c | |
| parent | 6e02b3e9327b7dbb063958d2b124b64fcb4bbe3f (diff) | |
| download | glibc-913201078502ad3f10043db02a8efce5d75387c2.tar.gz glibc-913201078502ad3f10043db02a8efce5d75387c2.tar.xz glibc-913201078502ad3f10043db02a8efce5d75387c2.zip | |
linux: Remove shmmax check from tst-sysvshm-linux
The shmmax expected value is tricky to check because kernel clamps it
to INT_MAX in two cases:
1. Compat symbols with IPC_64, i.e, 32-bit binaries running on 64-bit
kernels.
2. Default symbol without IPC_64 (defined as IPC_OLD within Linux) and
glibc always use IPC_64 for 32-bit ABIs (to support 64-bit time_t).
It means that 32-bit binaries running on 32-bit kernels will not see
shmmax being clamped.
And finding out whether the compat symbol is used would require checking
the underlying kernel against the current ABI. The shmall and shmmni
already provided enough coverage.
Checked on x86_64-linux-gnu and i686-linux-gnu. It should fix the
tst-sysvshm-linux failures on 32-bit kernels.
Diffstat (limited to 'sysdeps/hppa/dl-symaddr.c')
0 files changed, 0 insertions, 0 deletions