Jakub Kicinski d4e5db6452 tls: rx: device: keep the zero copy status with offload ...

The non-zero-copy path assumes a full skb with decrypted contents.
This means the device offload would have to CoW the data. Try
to keep the zero-copy status instead, copy the data to user space.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>

2022-07-26 14:38:51 -07:00

..

Kconfig

net/tls: Select SOCK_RX_QUEUE_MAPPING from TLS_DEVICE

2021-02-11 19:08:06 -08:00

Makefile

tls: rx: async: hold onto the input skb

2022-07-18 11:24:11 +01:00

tls_device_fallback.c

tls: create an internal header

2022-07-08 18:38:45 -07:00

tls_device.c

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

2022-07-21 13:03:39 -07:00

tls_main.c

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

2022-07-14 15:27:35 -07:00

tls_proc.c

tls: rx: add counter for NoPad violations

2022-07-11 19:48:33 -07:00

tls_strp.c

tls: rx: device: keep the zero copy status with offload

2022-07-26 14:38:51 -07:00

tls_sw.c

tls: rx: device: keep the zero copy status with offload

2022-07-26 14:38:51 -07:00

tls_toe.c

tls: create an internal header

2022-07-08 18:38:45 -07:00

tls.h

tls: rx: device: keep the zero copy status with offload

2022-07-26 14:38:51 -07:00

trace.c

net/tls: add tracing for device/offload events

2019-10-05 16:29:00 -07:00

trace.h

net/tls: add device decrypted trace point

2019-10-05 16:29:00 -07:00