[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #45130] "tv_sec" element of the timeval struct used in
From: |
Harsha Rajendran |
Subject: |
[lwip-devel] [bug #45130] "tv_sec" element of the timeval struct used in setsockopt should in fact be milliseconds and not seconds |
Date: |
Mon, 18 May 2015 13:38:29 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.152 Safari/537.36 |
URL:
<http://savannah.nongnu.org/bugs/?45130>
Summary: "tv_sec" element of the timeval struct used in
setsockopt should in fact be milliseconds and not seconds
Project: lwIP - A Lightweight TCP/IP stack
Submitted by: hrajendran
Submitted on: Mon 18 May 2015 01:38:28 PM GMT
Category: sockets/netconn
Severity: 3 - Normal
Item Group: Faulty Behaviour
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release:
lwIP version: 1.4.1
_______________________________________________________
Details:
The timeval struct which is passed to setsockopt has two fields, tv_sec and
tv_usec. However, on closer examination of the code, I found that tv_sec was
being treated as milliseconds and not seconds, like it is mentioned. Either
the struct should be modified to reflect this change, or the time expiration
logic must be changed.
Thanks
Harsha
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?45130>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
- [lwip-devel] [bug #45130] "tv_sec" element of the timeval struct used in setsockopt should in fact be milliseconds and not seconds,
Harsha Rajendran <=