Date: Fri, 28 Dec 2018 01:05:20 +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-7u9ocbegU6@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=3D167688 --- Comment #5 from Conrad Meyer <cem@freebsd.org> --- (In reply to Alan Somers from comment #4) > The signal does not interrupt the read(2). Hm, isn't that part of the bug? Signals are supposed to interrupt blocked = I/O; not interrupting explains the symptoms from the description mostly (sleep, = then signal handler, then read returns zero). --=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-167688-227-7u9ocbegU6>