From: David Miller <davem@davemloft.net>
To: opurdila@ixiacom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] tcp: update the netstamp_needed counter when cloning sockets
Date: Fri, 08 Jan 2010 00:00:34 -0800 (PST) [thread overview]
Message-ID: <20100108.000034.48682320.davem@davemloft.net> (raw)
In-Reply-To: <1262732790-16053-1-git-send-email-opurdila@ixiacom.com>
From: Octavian Purdila <opurdila@ixiacom.com>
Date: Wed, 6 Jan 2010 01:06:30 +0200
> This fixes a netstamp_needed accounting issue when the listen socket
> has SO_TIMESTAMP set:
>
> s = socket(AF_INET, SOCK_STREAM, 0);
> setsockopt(s, SOL_SOCKET, SO_TIMESTAMP, 1); -> netstamp_needed = 1
> bind(s, ...);
> listen(s, ...);
> s2 = accept(s, ...); -> netstamp_needed = 1
> close(s2); -> netstamp_needed = 0
> close(s); -> netstamp_needed = -1
>
> Signed-off-by: Octavian Purdila <opurdila@ixiacom.com>
Applied and queued up for -stable, thanks for fixing this!
prev parent reply other threads:[~2010-01-08 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 23:06 [PATCH] tcp: update the netstamp_needed counter when cloning sockets Octavian Purdila
2010-01-08 8:00 ` David Miller [this message]
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=20100108.000034.48682320.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).