diff options
| author | Christian Eggers <[email protected]> | 2020-10-12 11:35:41 +0200 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2020-10-13 17:18:18 -0700 |
| commit | 59e611a566e7cd48cf54b6777a11fe3f9c2f9db5 (patch) | |
| tree | 62c04464b008da04cf022ec31c106d4a3c85d846 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 254941f323702dbebe3f9145fdb1ab24c5bd23c1 (diff) | |
socket: fix option SO_TIMESTAMPING_NEW
The comparison of optname with SO_TIMESTAMPING_NEW is wrong way around,
so SOCK_TSTAMP_NEW will first be set and than reset again. Additionally
move it out of the test for SOF_TIMESTAMPING_RX_SOFTWARE as this seems
unrelated.
This problem happens on 32 bit platforms were the libc has already
switched to struct timespec64 (from SO_TIMExxx_OLD to SO_TIMExxx_NEW
socket options). ptp4l complains with "missing timestamp on transmitted
peer delay request" because the wrong format is received (and
discarded).
Fixes: 9718475e6908 ("socket: Add SO_TIMESTAMPING_NEW")
Signed-off-by: Christian Eggers <[email protected]>
Reviewed-by: Willem de Bruijn <[email protected]>
Reviewed-by: Deepa Dinamani <[email protected]>
Acked-by: Willem de Bruijn <[email protected]>
Acked-by: Deepa Dinamani <[email protected]>
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions