From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: davejwatson@fb.com, ilyal@mellanox.com, aviadye@mellanox.com,
borisp@mellanox.com, liranl@mellanox.com, matanb@mellanox.com,
netdev@vger.kernel.org, tom@herbertland.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
hannes@stressinduktion.org, alexei.starovoitov@gmail.com,
nmav@gnults.org, fridolin.pokorny@gmail.com
Subject: Re: [PATCH net-next 3/4] tls: kernel TLS support
Date: Fri, 26 May 2017 11:18:52 -0400 (EDT) [thread overview]
Message-ID: <20170526.111852.235696953256744250.davem@davemloft.net> (raw)
In-Reply-To: <1495808219.6465.118.camel@edumazet-glaptop3.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 26 May 2017 07:16:59 -0700
> On Wed, 2017-05-24 at 09:27 -0700, Dave Watson wrote:
>> Software implementation of transport layer security, implemented using ULP
>> infrastructure. tcp proto_ops are replaced with tls equivalents of sendmsg and
>> sendpage.
>
> ...
>
>> +
>> +int tls_sw_sendmsg(struct sock *sk, struct msghdr *msg, size_t size)
>> +{
> ...
>> +
>> + lock_sock(sk);
>> +
>> + /* Only one writer at a time is allowed */
>> + if (sk->sk_write_pending)
>> + return -EBUSY;
>
> Ouch...
Well, as I understand it, it is the same restriction userspace must
itself enforce either in the application or in the SSL library.
next prev parent reply other threads:[~2017-05-26 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1495642647.git.davejwatson@fb.com>
2017-05-24 16:26 ` [PATCH net-next 1/4] tcp: ULP infrastructure Dave Watson
2017-05-24 16:26 ` [PATCH net-next 2/4] tcp: export do_tcp_sendpages and tcp_rate_check_app_limited functions Dave Watson
2017-05-25 17:26 ` David Miller
2017-05-24 16:27 ` [PATCH net-next 3/4] tls: kernel TLS support Dave Watson
2017-05-26 14:16 ` Eric Dumazet
2017-05-26 15:18 ` David Miller [this message]
2017-05-26 15:49 ` Eric Dumazet
2017-05-24 16:27 ` [PATCH net-next 4/4] tls: Documentation Dave Watson
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=20170526.111852.235696953256744250.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davejwatson@fb.com \
--cc=eric.dumazet@gmail.com \
--cc=fridolin.pokorny@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=ilyal@mellanox.com \
--cc=linux-crypto@vger.kernel.org \
--cc=liranl@mellanox.com \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nmav@gnults.org \
--cc=tom@herbertland.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).