All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@free.fr>
To: Linux Netdev List <netdev@vger.kernel.org>
Subject: getsockopt(TCP_DEFER_ACCEPT) value change
Date: Tue, 05 Jan 2010 11:42:53 +0100	[thread overview]
Message-ID: <4B4317AD.1040302@free.fr> (raw)


Hi,

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;
}


             reply	other threads:[~2010-01-05 10:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 10:42 Daniel Lezcano [this message]
2010-01-05 13:40 ` getsockopt(TCP_DEFER_ACCEPT) value change Ilpo Järvinen
2010-01-05 14:11   ` Eric Dumazet
2010-01-05 14:45     ` Eric Dumazet
2010-01-05 15:45     ` Daniel Lezcano
2010-01-05 16:14       ` Eric Dumazet
2010-01-05 16:57         ` Daniel Lezcano
2010-01-05 20:29   ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B4317AD.1040302@free.fr \
    --to=daniel.lezcano@free.fr \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.