Page MenuHomeFreeBSD

getsockopt.2: clarify that SO_TIMESTAMP is not 100% reliable
ClosedPublic

Authored by asomers on Sep 11 2019, 6:59 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 30, 11:08 PM
Unknown Object (File)
Nov 15 2024, 10:26 PM
Unknown Object (File)
Nov 5 2024, 5:30 PM
Unknown Object (File)
Oct 27 2024, 1:03 AM
Unknown Object (File)
Oct 20 2024, 7:43 AM
Unknown Object (File)
Oct 6 2024, 10:35 PM
Unknown Object (File)
Oct 2 2024, 4:48 PM
Unknown Object (File)
Oct 2 2024, 4:39 AM
Subscribers

Details

Summary

getsockopt.2: clarify that SO_TIMESTAMP is not 100% reliable

When SO_TIMESTAMP is set, the kernel will attempt to attach a timestamp as
ancillary data to each IP datagram that is received on the socket. However,
it may fail, for example due to insufficient memory. In that case the
packet will still be received but not timestamp will be attached.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

May be add explicit language to the man page saying that resource shortage might prevent allocating the timestamp ? I believe it will be appreciated.

Explicitly state that a timestamp may not be returned

yuripv added inline comments.
lib/libc/sys/getsockopt.2
31 ↗(On Diff #61944)

Typo: September.

This revision is now accepted and ready to land.Sep 11 2019, 7:42 PM