From: Eric Dumazet <eric.dumazet@gmail.com>
To: Christoph Paasch <christoph.paasch@uclouvain.be>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, william.allen.simpson@gmail.com
Subject: Re: [PATCH net-next] Remove unused tw_cookie_values from tcp_timewait_sock
Date: Sun, 10 Mar 2013 17:06:10 +0100 [thread overview]
Message-ID: <1362931570.4051.34.camel@edumazet-glaptop> (raw)
In-Reply-To: <1362928719-13532-1-git-send-email-christoph.paasch@uclouvain.be>
On Sun, 2013-03-10 at 16:18 +0100, Christoph Paasch wrote:
> tw_cookie_values is never used in the TCP-stack.
>
> It was added by 435cf559f (TCPCT part 1d: define TCP cookie option,
> extend existing struct's), but already at that time it was not used at
> all, nor mentioned in the commit-message.
>
> Signed-off-by: Christoph Paasch <christoph.paasch@uclouvain.be>
> ---
> include/linux/tcp.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/include/linux/tcp.h b/include/linux/tcp.h
> index f28408c..515c374 100644
> --- a/include/linux/tcp.h
> +++ b/include/linux/tcp.h
> @@ -361,10 +361,6 @@ struct tcp_timewait_sock {
> #ifdef CONFIG_TCP_MD5SIG
> struct tcp_md5sig_key *tw_md5_key;
> #endif
> - /* Few sockets in timewait have cookies; in that case, then this
> - * object holds a reference to them (tw_cookie_values->kref).
> - */
> - struct tcp_cookie_values *tw_cookie_values;
> };
>
> static inline struct tcp_timewait_sock *tcp_twsk(const struct sock *sk)
Acked-by: Eric Dumazet <edumazet@google.com>
Actually, I am not sure TCPCT is really used...
next prev parent reply other threads:[~2013-03-10 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 15:18 [PATCH net-next] Remove unused tw_cookie_values from tcp_timewait_sock Christoph Paasch
2013-03-10 16:06 ` Eric Dumazet [this message]
2013-03-10 16:33 ` Christoph Paasch
2013-03-10 21:09 ` 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=1362931570.4051.34.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=christoph.paasch@uclouvain.be \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=william.allen.simpson@gmail.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