Hello Jakub, On Mon, 30 Aug 2021 at 13:39, Jakub Wilk <jwilk@xxxxxxxxx> wrote: > > * Alejandro Colomar <alx.manpages@xxxxxxxxx>, 2021-02-20, 11:05: > >In the Linux kernel, there's only one system call, and it's called > >exit (its entry point is sys_exit(), and can be called using > >syscall(SYS_exit, ...) *but don't*), BUT it implements the > >functionality of _exit() (as the standards call it; see above). > > To clarify, that's how it used to be, but since 2002ish there's also > sys_exit_group, and glibc's _exit() uses that. > > BTW, the exit_group.2 man page could use an update (possibly by merging > it into exit.2): it says that the "system call is is equivalent to > _exit(2) except that it terminates not only the calling thread, but all > threads in the calling process’s thread group", which isn't helpful > these days. Fair enough. I applied the patch below. Cheers, Michael diff --git a/man2/exit_group.2 b/man2/exit_group.2 index fc8cbe9ef..a6a6d9b26 100644 --- a/man2/exit_group.2 +++ b/man2/exit_group.2 @@ -39,9 +39,7 @@ glibc provides no wrapper for necessitating the use of .BR syscall (2). .SH DESCRIPTION -This system call is equivalent to -.BR _exit (2) -except that it terminates not only the calling thread, but all threads +This system call terminates all threads in the calling process's thread group. .SH RETURN VALUE This system call does not return. -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
