mirror of https://github.com/mkerrisk/man-pages
seccomp_unotify.2: srcfix: Add a further FIXME relating to SA_RESTART behavior
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
191350e602
commit
b183b6503c
|
@ -768,6 +768,15 @@ flag.
|
|||
.\" I mean, it's not like seccomp doesn't already expose weirdness with
|
||||
.\" syscall restarts. Not even arm64 compat agrees[3] with arm32 in this
|
||||
.\" regard. :(
|
||||
.
|
||||
.\" FIXME
|
||||
.\" Michael Kerrisk:
|
||||
.\" I wonder about the effect of this oddity for system calls that
|
||||
.\" are normally nonrestartable because they have timeouts. My
|
||||
.\" understanding is that the kernel doesn't restart those system
|
||||
.\" calls because it's impossible for the kernel to restart the call
|
||||
.\" with the right timeout value. I wonder what happens when those
|
||||
.\" system calls are restarted in the scenario we're discussing.)
|
||||
.SH BUGS
|
||||
If a
|
||||
.BR SECCOMP_IOCTL_NOTIF_RECV
|
||||
|
|
Loading…
Reference in New Issue