On Tue, 20 Sep 2022 08:50:10 +0200, Florian Obser wrote: > Is this somehow coming from the non-blocking connect diff? I can't spot > it though...
I don't think so, the ktrace shows that read(2) is returning 0 long after connect. If the socket was left in non-blocking mode I could see that causing problems but the file flags get restored. - todd
