aboutsummaryrefslogtreecommitdiff
path: root/scripts/cpp
diff options
context:
space:
mode:
authorAdhemerval Zanella <adhemerval.zanella@linaro.org>2022-01-27 16:45:18 -0300
committerAdhemerval Zanella <adhemerval.zanella@linaro.org>2022-02-01 15:52:41 -0300
commit489d0b8b32548bc569cd3067aebf98b030720753 (patch)
treec8c829acdd445cb8401b00fc5860977155a03700 /scripts/cpp
parente098446037da532d4a250efac9a813bc22f3669f (diff)
downloadglibc-489d0b8b32548bc569cd3067aebf98b030720753.tar.xz
glibc-489d0b8b32548bc569cd3067aebf98b030720753.zip
Linux: Only generate 64 bit timestamps for 64 bit time_t recvmsg/recvmmsg
The timestamps created by __convert_scm_timestamps only make sense for 64 bit time_t programs, 32 bit time_t programs will ignore 64 bit time_t timestamps since SO_TIMESTAMP will be defined to old values (either by glibc or kernel headers). Worse, if the buffer is not suffice MSG_CTRUNC is set to indicate it (which breaks some programs [1]). This patch makes only 64 bit time_t recvmsg and recvmmsg to call __convert_scm_timestamps. Also, the assumption to called it is changed from __ASSUME_TIME64_SYSCALLS to __TIMESIZE != 64 since the setsockopt might be called by libraries built without __TIME_BITS=64. The MSG_CTRUNC is only set for the 64 bit symbols, it should happen only if 64 bit time_t programs run older kernels. Checked on x86_64-linux-gnu and i686-linux-gnu. [1] https://github.com/systemd/systemd/pull/20567 Reviewed-by: Florian Weimer <fweimer@redhat.com> (cherry picked from commit 948ce73b31fdb0860bcec4b8e62b14e88234f98a)
Diffstat (limited to 'scripts/cpp')
0 files changed, 0 insertions, 0 deletions