Re: [PATCH net 1/9] net/tls: Bound time spent on no-data records in tls_sw_read_sock()
"Chuck Lever" <[email protected]> Mon, 03 Aug 2026 20:35:54 -0400
| Newsgroups | org.kernel.vger.netdev,org.kernel.vger.linux-kselftest |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Aug 3, 2026, at 6:39 PM, Jakub Kicinski wrote: > On Sun, 26 Jul 2026 20:33:29 -0400 Chuck Lever wrote: >> +/* Bound the time that consecutive empty ingress data records keep >> + * the socket lock held without releasing it. >> + */ >> +#define TLS_RX_NODATA_NS NSEC_PER_MSEC > > A time bound is a bad idea in the kernel, a softirq can easily=20 > take >1msec and turn 2 consecutive zero length records into > a fatal error for the connection. I don=E2=80=99t have a particular dog in this race, but you and Sabrina = need to thumb wrestle to decide which way this needs to go. My original thought was to use a count of zero-length packets. --=20 Chuck Lever