Date: Sat, 18 Jul 2020 13:16:06 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 248065] Linuxulator: 32-bit compat + send with MSG_NOSIGNAL Message-ID: <bug-248065-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248065 Bug ID: 248065 Summary: Linuxulator: 32-bit compat + send with MSG_NOSIGNAL Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: iwtcex@gmail.com CC: trasz@FreeBSD.org Attachment #216539 text/plain mime type: Created attachment 216539 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D216539&action= =3Dedit minimal repro Apparently, with a sufficiently large payload and the MSG_NOSIGNAL flag, blocking send turns out not quite as blocking as expected. So far this is o= nly observable with 32-bit Linux applications: % /compat/linux/usr/bin/cc -DSERVER -DCLIENT -std=3Dc99 -Wall -m32 eagain-b= ug.c -pthread -o eagain-bug % ./eagain-bug server started client started connection accepted [server] Sending 100000 bytes... [server] sent: 49032 [server] Sending 100000 bytes... [server] sent: -1 [server] send: Resource temporarily unavailable See attachment for the code. (Or grab it from https://github.com/shkhln/unexpected-eagain.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248065-227>