On Tue, Oct 13, 2026, [email protected] wrote: > > [Severity: High] > Can callers that never get a signal still be held in tls_sw_recvmsg() > for as long as the peer keeps sending empty records?
Yes, and this series leaves that hold in place. The cover letter covers this case, so agentic review might have missed it: an in-kernel caller of sock_recvmsg() cannot take a signal, so a flood holds that caller as it does today, and SO_RCVTIMEO does not bound these calls. This patch ends the hang for a reader that a signal can reach. -- Chuck Lever (Come to NFS bake-a-thon! https://nfsv4bat.org)
