From: Eric Dumazet <edumazet@google.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/4] tcp: listener refactor part 16
Date: Mon, 23 Mar 2015 21:34:22 -0700 [thread overview]
Message-ID: <1427171666-30585-1-git-send-email-edumazet@google.com> (raw)
I added const qualifiers to various md5 methods, as I expect
to call them on behalf of request sock traffic even if
the listener socket is not locked. This seems ok, but adding
const makes the contract clearer. Note a good reduction
of code size thanks to request/establish sockets convergence.
Eric Dumazet (4):
tcp: use C99 initializers in new_state[]
tcp: md5: input path is run under rcu protected sections
tcp: md5: remove request sock argument of calc_md5_hash()
tcp: md5: get rid of tcp_v[46]_reqsk_md5_lookup()
include/net/tcp.h | 45 +++++++++++++++++++---------------------
net/ipv4/tcp.c | 25 +++++++++++-----------
net/ipv4/tcp_ipv4.c | 57 +++++++++++++++------------------------------------
net/ipv4/tcp_output.c | 6 +++---
net/ipv6/tcp_ipv6.c | 56 +++++++++++++++-----------------------------------
5 files changed, 71 insertions(+), 118 deletions(-)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-03-24 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 4:34 Eric Dumazet [this message]
2015-03-24 4:34 ` [PATCH net-next 1/4] tcp: use C99 initializers in new_state[] Eric Dumazet
2015-03-24 4:34 ` [PATCH net-next 2/4] tcp: md5: input path is run under rcu protected sections Eric Dumazet
2015-03-24 4:34 ` [PATCH net-next 3/4] tcp: md5: remove request sock argument of calc_md5_hash() Eric Dumazet
2015-03-24 4:34 ` [PATCH net-next 4/4] tcp: md5: get rid of tcp_v[46]_reqsk_md5_lookup() Eric Dumazet
2015-03-24 19:02 ` [PATCH net-next 0/4] tcp: listener refactor part 16 David Miller
2015-03-24 19:14 ` David Miller
2015-03-24 21:28 ` Eric Dumazet
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=1427171666-30585-1-git-send-email-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox