Open xlz opened 9 years ago
great catch.
since nuse_current_ns() is the source of jiffies, used by Linux kernel part, I intended to use CLOCK_MONOTONIC to avoid discontinuous time jump.
I would really like to see how this issue can be solved transparently but didn't come up with the idea.
The cause is that timestamps obtained with SO_TIMESTAMP are from CLOCK_MONOTONIC (~986000 second) and are then compared with CLOCK_REALTIME timestamps from gettimeofday.
Changing
CLOCK_MONOTONIC
innuse.c
toCLOCK_REALTIME
seems to suppress this warning, but it might not be the correct fix.