netdev - Problem with semantics?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <OFF8FEF8BA.07073375-ONC2257336.005DB73A-C2257336.005E19ED@il.ibm.com>
Date:	Mon, 13 Aug 2007 20:07:50 +0300
From:	Shay Goikhman <GOIKHMAN@...ibm.com>
To:	netdev@...r.kernel.org
Cc:	davem@...emloft.net
Subject: Problem with semantics?

Dear Linux maintainers,

 I'm doing :

      setsockopt(s,  SO_RCVTIMEO, t1 );                  // set time-out
t1 on socket while block receiving on it
      select(,,, &fd_set_including(s), .., &errs, t2);      // block till
receive or time-out  t 2 jointly on a set of sockets

Apparently, I could no find reference on the coupled behavior of the two
above statements in Linux documentation.
As I understand the blocking semantics, I would expect  that  if t1<t2 ,
select should return after t1 with the descriptor 's' in 'errs' if 's' does
not become readable in the t1 interval.

It is not so in life -- select ignores t1 altogether.

Do you have some enlightening knowledge on the matter?
Thanks,
-Shay

-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html