Date: Wed, 03 Apr 2019 15:43:00 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 167688] [fusefs] Incorrect signal handling with direct_io Message-ID: <bug-167688-227-OypB7N95zq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-167688-227@https.bugs.freebsd.org/bugzilla/> References: <bug-167688-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=167688 --- Comment #8 from Alan Somers <asomers@FreeBSD.org> --- Firstly, let me thank you for such a good reproduction case. This is certainly the best reproduction case I've ever seen for a user-reported fuse bug, and it ranks highly for the best reproduction cases I've ever seen for a user-reported bug on any project. That said, I'm going to close the issue because I can't reproduce it. Judging by the date of your post, you were probably using the sysutils/fusefs-kmod port, which has been replaced by the in-tree fusefs(5) driver. There have been many improvements. I plan to tackle interruptibility in bug 236530. -- 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-167688-227-OypB7N95zq>