diff options
| author |   Heiko Carstens <hca@linux.ibm.com> | 2021-03-24 20:23:55 +0100 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2021-03-25 21:57:26 +0100 |
| commit | 5b43bd184530af6b868d8273b0a743a138d37ee8 (patch) | |
| tree | f8420c59764e10b88616096c178fd8875d5d2ee9 /MAINTAINERS | |
| parent | s390/vdso: fix tod_steering_delta type (diff) | |
| download | wireguard-linux-5b43bd184530af6b868d8273b0a743a138d37ee8.tar.xz wireguard-linux-5b43bd184530af6b868d8273b0a743a138d37ee8.zip | |
s390/vdso: fix initializing and updating of vdso_data
Li Wang reported that clock_gettime(CLOCK_MONOTONIC_RAW, ...) returns
incorrect values when time is provided via vdso instead of system call:
vdso_ts_nsec = 4484351380985507, vdso_ts.tv_sec = 4484351, vdso_ts.tv_nsec = 380985507
sys_ts_nsec = 1446923235377, sys_ts.tv_sec = 1446, sys_ts.tv_nsec = 923235377
Within the s390 specific vdso function __arch_get_hw_counter() reads
tod clock steering values from the arch_data member of the passed in
vdso_data structure.
Problem is that only for the CS_HRES_COARSE vdso_data arch_data is
initialized and gets updated. The CS_RAW specific vdso_data does not
contain any valid tod_clock_steering information, which explains the
different values.
Fix this by initializing and updating all vdso_datas.
Reported-by: Li Wang <liwang@redhat.com>
Tested-by: Li Wang <liwang@redhat.com>
Fixes: 1ba2d6c0fd4e ("s390/vdso: simplify __arch_get_hw_counter()")
Link: https://lore.kernel.org/linux-s390/YFnxr1ZlMIOIqjfq@osiris
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions