summaryrefslogtreecommitdiffstats
path: root/include/net
diff options
context:
space:
mode:
authorJakub Kicinski <jakub.kicinski@netronome.com>2019-11-27 12:16:43 -0800
committerDavid S. Miller <davem@davemloft.net>2019-11-28 22:40:29 -0800
commit9e5ffed37df68d0ccfb2fdc528609e23a1e70ebe (patch)
tree92fafe20cc6e67a73043b9bf46711e65934eda85 /include/net
parent65190f77424d7b82c4aad7326c9cce6bd91a2fcc (diff)
downloadtalos-op-linux-9e5ffed37df68d0ccfb2fdc528609e23a1e70ebe.tar.gz
talos-op-linux-9e5ffed37df68d0ccfb2fdc528609e23a1e70ebe.zip
net/tls: remove the dead inplace_crypto code
Looks like when BPF support was added by commit d3b18ad31f93 ("tls: add bpf support to sk_msg handling") and commit d829e9c4112b ("tls: convert to generic sk_msg interface") it broke/removed the support for in-place crypto as added by commit 4e6d47206c32 ("tls: Add support for inplace records encryption"). The inplace_crypto member of struct tls_rec is dead, inited to zero, and sometimes set to zero again. It used to be set to 1 when record was allocated, but the skmsg code doesn't seem to have been written with the idea of in-place crypto in mind. Since non trivial effort is required to bring the feature back and we don't really have the HW to measure the benefit just remove the left over support for now to avoid confusing readers. Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com> Reviewed-by: Simon Horman <simon.horman@netronome.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/net')
-rw-r--r--include/net/tls.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/net/tls.h b/include/net/tls.h
index 6ed91e82edd0..9d32f7ce6b31 100644
--- a/include/net/tls.h
+++ b/include/net/tls.h
@@ -100,7 +100,6 @@ struct tls_rec {
struct list_head list;
int tx_ready;
int tx_flags;
- int inplace_crypto;
struct sk_msg msg_plaintext;
struct sk_msg msg_encrypted;
OpenPOWER on IntegriCloud