Date: Tue, 09 Aug 2022 08:05:10 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 258056] lang/go118: musn't poll /dev/fuse Message-ID: <bug-258056-227-PHVsbfKj7z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258056-227@https.bugs.freebsd.org/bugzilla/> References: <bug-258056-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=3D258056 Yuval Pavel Zholkover <paulzhol@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paulzhol@gmail.com --- Comment #26 from Yuval Pavel Zholkover <paulzhol@gmail.com> --- Created attachment 235792 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D235792&action= =3Dedit bazil/fuse workaround Hi, As I mentioned in the upstream issue https://github.com/golang/go/issues/54= 100, there are a few issues here. The Go runtime has a bug in which file descriptors in blocking mode can get added to the network poller. This is what the https://go-review.googlesource.com/c/go/+/420334 fix is about. However I think there's an additional bug in the /dev/fuse character device: The call to fcntl(<fd>,F_SETFL,O_RDWR|O_NONBLOCK) is reporting an ENODEV (Operation not supported by device) error, but the device is still put into non-blocking mode. Causing reads to return EAGAIN. These EAGAIN errors are unexpected by the bazil/fuse package rclone uses. bazil/fuse is doing blocking operations only anyway, so there's a simple workaround which avoids calling fcntl in the first place (attached). --=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-258056-227-PHVsbfKj7z>