From: David Miller <davem@davemloft.net>
To: borisp@mellanox.com
Cc: kuba@kernel.org, john.fastabend@gmail.com, daniel@iogearbox.net,
tariqt@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] tls: add zerocopy device sendpage
Date: Tue, 14 Jul 2020 13:38:49 -0700 (PDT) [thread overview]
Message-ID: <20200714.133849.786362008823993310.davem@davemloft.net> (raw)
In-Reply-To: <e538c2bc-b8b5-c5d9-05a3-a385d2c809e4@mellanox.com>
From: Boris Pismenny <borisp@mellanox.com>
Date: Tue, 14 Jul 2020 10:31:25 +0300
> At the time, Dave objected when we presented this on the netdev conference,
> and we didn't want to delay the entire series just to argue this point. It's
> all a matter of timing and priorities. Now we have an ASIC that uses this API,
> and I'd like to show the best possible outcome, and not the best possible given
> an arbitrary limitation that avoids an error where the user does something
> erroneous.
It's not arbitrary, and what the user is doing is not "erroneous".
Imagine a userspace fileserver using sendpage, other users in the system can
write to the files while the fileserver sends it off to a client.
And that's perfectly legitimate and fine. We get the IP checksums
correct, everything works.
And, therefore, if TLS is used, the signatures should be correct too.
And I'm also happy to hear that from the very start I was against an
implementation that would knowingly send incorrect signatures.
I'm not moving on this point, sorry. Correctness over performance.
next prev parent reply other threads:[~2020-07-14 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1594550649-3097-1-git-send-email-borisp@mellanox.com>
[not found] ` <20200712.153233.370000904740228888.davem@davemloft.net>
2020-07-13 7:49 ` [PATCH] tls: add zerocopy device sendpage Boris Pismenny
2020-07-13 19:05 ` David Miller
2020-07-13 22:15 ` Boris Pismenny
2020-07-13 22:59 ` Jakub Kicinski
2020-07-14 7:31 ` Boris Pismenny
2020-07-14 16:23 ` Jakub Kicinski
2020-07-14 20:38 ` David Miller [this message]
2020-07-14 1:02 ` David Miller
2020-07-14 7:27 ` Boris Pismenny
2020-07-14 20:42 ` David Miller
2020-07-14 20:56 ` Boris Pismenny
2020-07-12 10:53 Boris Pismenny
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=20200714.133849.786362008823993310.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=borisp@mellanox.com \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tariqt@mellanox.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).