Commit 511aa37
committed
complete SO_TIMESTAMPNS to SO_TIMESTAMP fallback
Commit e866063 added a
fallback from setting the socket option SO_TIMESTAMPNS to
setting the socket option SO_TIMESTAMP if the nanosecond
timestamp option could not be set. But it did not add
code to also look for the control message related to
SO_TIMESTAMP. Thus microsecond timestamps were requested,
but not read.
This commit adds the missing code to read microsecond
timestamp control messages.
The problem was reported in GitHub issue #374 by @payload.1 parent cb83286 commit 511aa37
2 files changed
+21
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
1 | 9 | | |
2 | 10 | | |
3 | 11 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1284 | 1284 | | |
1285 | 1285 | | |
1286 | 1286 | | |
| 1287 | + | |
| 1288 | + | |
| 1289 | + | |
| 1290 | + | |
| 1291 | + | |
| 1292 | + | |
| 1293 | + | |
| 1294 | + | |
1287 | 1295 | | |
1288 | 1296 | | |
1289 | 1297 | | |
| |||
2105 | 2113 | | |
2106 | 2114 | | |
2107 | 2115 | | |
| 2116 | + | |
2108 | 2117 | | |
2109 | 2118 | | |
2110 | 2119 | | |
2111 | 2120 | | |
2112 | 2121 | | |
2113 | 2122 | | |
2114 | 2123 | | |
| 2124 | + | |
| 2125 | + | |
| 2126 | + | |
| 2127 | + | |
2115 | 2128 | | |
2116 | 2129 | | |
2117 | 2130 | | |
| |||
0 commit comments