Date: Mon, 03 Jul 2017 22:07:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 220459] lio_listio(2) doesn't support SIGEV_THREAD Message-ID: <bug-220459-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220459 Bug ID: 220459 Summary: lio_listio(2) doesn't support SIGEV_THREAD 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 lio_listio(2) returns EINVAL when its sig->sigev_notify is SIGEV_THREAD. T= hat error gets returned from kern_lio_listio. The lio_listio(2) man page makes= no mention of this limitation. In fact, it says that SIGEV_THREAD _is_ suppor= ted. For other aio(4) functions, SIGEV_THREAD is handled in librt and implement= ed using SIGEV_THREAD_ID, which is what the kernel actually sees. But lio_lis= tio doesn't go through librt. Instead, it's a direct syscall. Either the man page should be updated, or lio_listio should gain a librt wrapper just like aio_read(2) and friends. --=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-220459-8>