From 4a66e5e1bbb0307c3ae32fed149a37d5c3168152 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Fri, 29 May 2015 07:23:47 -0600 Subject: [PATCH] Update ChangeLog --- ChangeLog | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/ChangeLog b/ChangeLog index 2575240c364..3b136b3d654 100755 --- a/ChangeLog +++ b/ChangeLog @@ -10456,3 +10456,12 @@ okay, undoing the good things that net_startmonitor did and causing the socket to be marked as connected. This behavior was noted by Pelle Windestam (2015-05-28). + * net/socket and net/utils: setsockopt() fails when setting timeouts + to values less that an 100 msec. That is because the timeout is + limited to stops of 1 decisecond and because the conversion of + structure timeval was truncating the microsecond remainder. The + utility net_timeval2dsec now accespts and option to determin how it + handles the remainder: truncate, discarding the remainder, use the + remainder to round to the closed decisecond value, or use any non-zero + remainder to the next larger whole decisecond value. Bug discovered + by Librae (2015-05-29).