Date: Fri, 30 Jun 2017 21:53:05 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220398] lio_listio(2) never sends asynchronous notification if nent==0 Message-ID: <bug-220398-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220398 Bug ID: 220398 Summary: lio_listio(2) never sends asynchronous notification if nent=3D=3D0 Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: asomers@FreeBSD.org Created attachment 183968 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D183968&action= =3Dedit Reproduction program It may seem stupid, but you can call lio_listio(2) with an empty aiocb list= . I would naively expect lio_listio to do nothing and return in that case. Ind= eed, that's what it does when mode =3D=3D LIO_WAIT. However, if mode =3D=3D LIO= _NOWAIT, then asynchronous notifications never get delivered. With SIGEV_KEVENT, no kevent is ever delivered, and with SIGEV_SIGNAL, no signal is ever delivere= d.=20 I haven't checked other SIGEV_ values. The attached program demonstrates the problem: it calls lio_listio with LIO_NOWAIT and notification via SIGTERM. But no signal ever gets delivered= , so the program exits normally. jhb feels that the Open Group's specification is ambiguous on this point, b= ut that sending asynchronous notification immediately would be sensible. --=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-220398-8>