From: Ilya Lesokhin <ilyal@mellanox.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: davejwatson@fb.com, aviadye@mellanox.com,
Ilya Lesokhin <ilyal@mellanox.com>
Subject: [PATCH v2 net-next 0/3] Use correct sk->sk_prot for IPV6
Date: Tue, 15 Aug 2017 14:08:37 +0300 [thread overview]
Message-ID: <1502795320-22538-1-git-send-email-ilyal@mellanox.com> (raw)
The tls ulp overrides sk->prot with a new tls specific proto structs.
The tls specific structs were previously based on the ipv4 specific
tcp_prot sturct.
As a result, attaching the tls ulp to an ipv6 tcp socket replaced
some ipv6 callback with the ipv4 equivalents.
This patch adds ipv6 tls proto structs and uses them when
attached to ipv6 sockets.
Changes since v1:
- TLS now dependes on IPV6
This fixes complication issues when TLS is built-in and IPV6 is a module.
The downside should be small as it is unlikely that there are kernel TLS
users who can't afford to include IPV6 in thier kernel.
- tls_init now checks sk->sk_prot directly
This is somewhat safer then checking indirectly through sk->sk_family
Ilya Lesokhin (3):
ipv6: Prevent unexpected sk->sk_prot changes
net: Export tcpv6_prot
tls: Use correct sk->sk_prot for IPV6
net/ipv6/ipv6_sockglue.c | 12 ++++++++++++
net/ipv6/tcp_ipv6.c | 1 +
net/tls/Kconfig | 1 +
net/tls/tls_main.c | 50 ++++++++++++++++++++++++++++++++++++------------
4 files changed, 52 insertions(+), 12 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-08-15 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 11:08 Ilya Lesokhin [this message]
2017-08-15 11:08 ` [PATCH v2 net-next 1/3] ipv6: Prevent unexpected sk->sk_prot changes Ilya Lesokhin
2017-08-15 11:39 ` Eric Dumazet
2017-08-15 11:59 ` Eric Dumazet
2017-08-15 13:08 ` Boris Pismenny
2017-08-15 14:45 ` Eric Dumazet
2017-08-23 7:49 ` Ilya Lesokhin
2017-08-15 11:08 ` [PATCH v2 net-next 2/3] net: Export tcpv6_prot Ilya Lesokhin
2017-08-15 11:08 ` [PATCH v2 net-next 3/3] tls: Use correct sk->sk_prot for IPV6 Ilya Lesokhin
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=1502795320-22538-1-git-send-email-ilyal@mellanox.com \
--to=ilyal@mellanox.com \
--cc=aviadye@mellanox.com \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--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.