Re: getsockopt(TCP_DEFER_ACCEPT) value change

[Eric Dumazet <eric.dumazet@gmail.com>]

Le 05/01/2010 14:40, Ilpo Järvinen a écrit :
> On Tue, 5 Jan 2010, Daniel Lezcano wrote:
> 
>> I noticed a change in the value returned by the getsockopt for the
>> TCP_DEFER_ACCEPT option with a 2.6.32 kernel. The value retrieved with the
>> getsockopt is different from the one specified with the setsockopt. Is it an
>> expected behaviour ?
>>
>> I saw there were  changes around the TCP_DEFER_ACCEPT option with the number
>> of attempts converted to a number of seconds.
>>
>> The following program is working fine with a 2.6.31 but fails with a 2.6.32
>> kernel.
>>
>> Thanks
>>  -- Daniel
>>
>> #include <stdio.h>
>> #include <sys/socket.h>
>> #include <netinet/in.h>
>> #include <netinet/tcp.h>
>>
>> int main(int argc, char *argv[])
>> {
>>    int val1 = 12, val2;
>>    socklen_t len = sizeof(val2);
>>    int fd;
>>      fd = socket(PF_INET, SOCK_STREAM, 0);
>>    if (fd < 0) {
>>        perror("socket");
>>        return -1;
>>    }
>>      if (setsockopt(fd, SOL_TCP, TCP_DEFER_ACCEPT, &val1, sizeof(val1))) {
>>        perror("setsockopt");
>>        return -1;
>>    }
>>      if (getsockopt(fd, SOL_TCP, TCP_DEFER_ACCEPT, &val2, &len)) {
>>        perror("getsockopt");
>>        return -1;
>>    }
>>
>>    if (val1 != val2) {
>>        fprintf(stderr, "error %d != %d\n", val1, val2);
>>        return -1;
>>    }
>>
>>    return 0;
>> }
> 
> Added Cc.
> 
> I don't think this change was intentional. ...However, is this difference 
> particularly significant besides failing such a test program? The actual 
> value now returned by the getsockopt is more accurate than what the
> userspace initially provided.
> 
> In general, I wonder if there's something that mandates that a set/get 
> pair of value should be equal?
> 

Nothing... really... we can round the value, and we indeed round it in 2.6.32

defer value is given in second by user, and converted to number of retransmits by kernel.

Program assumption is wrong.