[PATCH 1/2] seccomp_unotify.2: confirm listener limits and signal behavior

[Simon Essien <champbreed1@gmail.com>]

- Remove FIXME regarding the single-listener limit. Verification
  via test program confirms the kernel returns EBUSY as documented.
- Remove FIXME regarding SA_RESTART oddity. The behavior is
  established and documented; the internal query is no longer required.
---
 man/man2/seccomp_unotify.2 | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/man/man2/seccomp_unotify.2 b/man/man2/seccomp_unotify.2
index b3aedad4b..f1ff13513 100644
--- a/man/man2/seccomp_unotify.2
+++ b/man/man2/seccomp_unotify.2
@@ -89,8 +89,6 @@ Consequently, the return value of the (successful)
 call is a new "listening"
 file descriptor that can be used to receive notifications.
 Only one "listening" seccomp filter can be installed for a thread.
-.\" FIXME
-.\" Is the last sentence above correct?
 .\"
 .\" Kees Cook (25 Oct 2020) notes:
 .\"
@@ -1148,16 +1146,6 @@ that would
 normally be restarted by the
 .B SA_RESTART
 flag.
-.\" FIXME
-.\" About the above, Kees Cook commented:
-.\"
-.\" Does this need fixing? I imagine the correct behavior for this case
-.\" would be a response to _SEND of EINPROGRESS and the target would see
-.\" EINTR normally?
-.\"
-.\" 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:
-- 
2.51.0