Date: Fri, 28 Dec 2018 01:12:33 +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-5npffH1wpn@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 #7 from Conrad Meyer <cem@freebsd.org> --- (In reply to Conrad Meyer from comment #6) Sigh. Yes, we PCATCH, *but*: 314 static int 315 fticket_wait_answer(struct fuse_ticket *ftick) 316 { ... 334 fuse_block_sigs(&tset); 335 err =3D msleep(ftick, &ftick->tk_aw_mtx, PCATCH, "fu_ans", 336 data->daemon_timeout * hz); 337 fuse_restore_sigs(&tset); We block all signals but SIGKILL. --=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-5npffH1wpn>