From: Michael Kerrisk Date: Mon, 26 Oct 2020 09:45:24 +0000 (+0100) Subject: seccomp_user_notif.2: srcfix: Add a further FIXME relating to SA_RESTART behavior X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f0997bafc5d5cde84022efe08c9bab75b8e01689;p=thirdparty%2Fman-pages.git seccomp_user_notif.2: srcfix: Add a further FIXME relating to SA_RESTART behavior Signed-off-by: Michael Kerrisk --- diff --git a/man2/seccomp_user_notif.2 b/man2/seccomp_user_notif.2 index 37325f6ae8..f3f72929ee 100644 --- a/man2/seccomp_user_notif.2 +++ b/man2/seccomp_user_notif.2 @@ -772,6 +772,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