Date: Sun, 10 May 2020 19:43:23 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 246350] kqueue fails to report pipe writable after the read end is closed Message-ID: <bug-246350-227-7fpeTdgMcz@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246350-227@https.bugs.freebsd.org/bugzilla/> References: <bug-246350-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246350 --- Comment #2 from Nathaniel Smith <njs@pobox.com> --- I just tested on using the latest 12.1-STABLE release snapshot (FreeBSD-12.1-STABLE-amd64-20200507-r360721-disc1.iso). Since r360721 is hi= gher than r360380, I would expect this to include the fix? But I still get the same result: root@:/host-files # uname -a FreeBSD 12.1-STABLE FreeBSD 12.1-STABLE r360721 GENERIC amd64 root@:/host-files # python3.8 notes-to-self/fbsd-pipe-close-notify.py filling pipe buffer select() says the write pipe is NOT writable closing read end of pipe select() says the write pipe is writable waiting for kqueue to report the write end is writable [... hang ...] --=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-246350-227-7fpeTdgMcz>