Hi Helge,
On Sun, Nov 17, 2024 at 10:46:25AM GMT, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: I<exit_signal.> → I<exit_signal>.
>
> "B<CLONE_THREAD> or B<CLONE_PARENT> was specified in the I<flags> mask, but a "
> "signal was specified in I<exit_signal>."
>
This was fixed in
commit befb4aaa6d3e2bf1bf975a3585c23b863a534092
Author: Alejandro Colomar <alx@xxxxxxxxxx>
Date: Wed Nov 1 16:02:49 2023 +0100
clone.2: ffix
Fixes: 184ecd225079 ("clone.2: Note EINVAL when exit_signal + bad flags")
Reported-by: Helge Kreutzmann <debian@xxxxxxxxxxxxx>
Cc: Mario Blaettermann <mario.blaettermann@xxxxxxxxx>
Signed-off-by: Alejandro Colomar <alx@xxxxxxxxxx>
diff --git a/man2/clone.2 b/man2/clone.2
index e5ba4fc44..8e5eae806 100644
--- a/man2/clone.2
+++ b/man2/clone.2
@@ -1449,7 +1449,7 @@ .SH ERRORS
was specified in the
.I flags
mask, but a signal was specified in
-.I exit_signal.
+.IR exit_signal .
.TP
.BR EINVAL " (AArch64 only, Linux 4.6 and earlier)"
.I stack
Cheers,
Alex
--
<https://www.alejandro-colomar.es/>
Attachment:
signature.asc
Description: PGP signature
