LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

seccomp_unotify.2: Add BUGS section describing SECCOMP_IOCTL_NOTIF_RECV bug 

Tycho Andersen confirmed that this issue is present.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2020-09-30 22:32:46 +02:00
parent 72a8602617
commit d85217eff7
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man2/seccomp_unotify.2
View File

@ -349,6 +349,8 @@ was being generated.
.\" Is this expected behavior? It seems to me rather
.\" desirable that SECCOMP_IOCTL_NOTIF_RECV should give an error
.\" if the target process has terminated.
.\"
.\" For now, this behavior is documented in BUGS.
.TP
.BR SECCOMP_IOCTL_NOTIF_ID_VALID " (since Linux 5.0)"
This operation can be used to check that a notification ID
@ -562,6 +564,14 @@ these interfaces indicate that the file descriptor is readable.
.\" Interestingly, after the event had been received, the file
.\" descriptor indicates as writable (verified from the source
.\" code and by experiment). How is this useful?
.SH BUGS
If a
.BR SECCOMP_IOCTL_NOTIF_RECV
.BR ioctl (2)
operation is performed after the target process terminates, then the
.BR ioctl (2)
call simply blocks (rather than returning an error to indicate that the
target process no longer exists).
.SH EXAMPLES
The (somewhat contrived) program shown below demonstrates the use of
the interfaces described in this page.