Vakul Garg 4504ab0e6e net/tls: Inform user space about send buffer availability ... A previous fix ("tls: Fix write space handling") assumed that user space application gets informed about the socket send buffer availability when tls_push_sg() gets called. Inside tls_push_sg(), in case do_tcp_sendpages() returns 0, the function returns without calling ctx->sk_write_space. Further, the new function tls_sw_write_space() did not invoke ctx->sk_write_space. This leads to situation that user space application encounters a lockup always waiting for socket send buffer to become available. Rather than call ctx->sk_write_space from tls_push_sg(), it should be called from tls_write_space. So whenever tcp stack invokes sk->sk_write_space after freeing socket send buffer, we always declare the same to user space by the way of invoking ctx->sk_write_space. Fixes: 7463d3a2db ("tls: Fix write space handling") Signed-off-by: Vakul Garg <vakul.garg@nxp.com> Reviewed-by: Boris Pismenny <borisp@mellanox.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2019-03-13 14:16:44 -07:00
..
Kconfig
Makefile
tls_device_fallback.c
tls_device.c	net/tls: Inform user space about send buffer availability	2019-03-13 14:16:44 -07:00
tls_main.c	net/tls: Inform user space about send buffer availability	2019-03-13 14:16:44 -07:00
tls_sw.c	tls: Fix tls_device receive	2019-03-03 22:10:16 -08:00