Re: [net v3 0/2] net/tls: fix encryption error path

2020-05-21 Thread David Miller
From: Vadim Fedorenko Date: Wed, 20 May 2020 11:41:42 +0300 > The problem with data stream corruption was found in KTLS > transmit path with small socket send buffers and large > amount of data. bpf_exec_tx_verdict() frees open record > on any type of error including EAGAIN, ENOMEM and ENOSPC >

Re: [net v3 0/2] net/tls: fix encryption error path

2020-05-21 Thread Pooja Trivedi
On Wed, May 20, 2020 at 4:46 PM Jakub Kicinski wrote: > > On Wed, 20 May 2020 11:41:42 +0300 Vadim Fedorenko wrote: > > The problem with data stream corruption was found in KTLS > > transmit path with small socket send buffers and large > > amount of data. bpf_exec_tx_verdict() frees open record >

Re: [net v3 0/2] net/tls: fix encryption error path

2020-05-20 Thread Jakub Kicinski
On Wed, 20 May 2020 11:41:42 +0300 Vadim Fedorenko wrote: > The problem with data stream corruption was found in KTLS > transmit path with small socket send buffers and large > amount of data. bpf_exec_tx_verdict() frees open record > on any type of error including EAGAIN, ENOMEM and ENOSPC > whil

[net v3 0/2] net/tls: fix encryption error path

2020-05-20 Thread Vadim Fedorenko
The problem with data stream corruption was found in KTLS transmit path with small socket send buffers and large amount of data. bpf_exec_tx_verdict() frees open record on any type of error including EAGAIN, ENOMEM and ENOSPC while callers are able to recover this transient errors. Also wrong erro