2023-01-12 21:58:51 +08:00
|
|
|
/* Tests for posix_spawn signal handling.
|
2024-01-02 02:12:26 +08:00
|
|
|
Copyright (C) 2023-2024 Free Software Foundation, Inc.
|
2023-01-12 21:58:51 +08:00
|
|
|
This file is part of the GNU C Library.
|
|
|
|
|
|
|
|
The GNU C Library is free software; you can redistribute it and/or
|
|
|
|
modify it under the terms of the GNU Lesser General Public
|
|
|
|
License as published by the Free Software Foundation; either
|
|
|
|
version 2.1 of the License, or (at your option) any later version.
|
|
|
|
|
|
|
|
The GNU C Library is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
Lesser General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Lesser General Public
|
|
|
|
License along with the GNU C Library; if not, see
|
|
|
|
<http://www.gnu.org/licenses/>. */
|
|
|
|
|
|
|
|
#include <assert.h>
|
|
|
|
#include <getopt.h>
|
|
|
|
#include <spawn.h>
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
|
|
|
#include <support/check.h>
|
|
|
|
#include <support/xsignal.h>
|
|
|
|
#include <support/xunistd.h>
|
posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349)
Returning a pidfd allows a process to keep a race-free handle for a
child process, otherwise, the caller will need to either use pidfd_open
(which still might be subject to TOCTOU) or keep the old racy interface
base on pid_t.
To correct use pifd_spawn, the kernel must support not only returning
the pidfd with clone/clone3 but also waitid (P_PIDFD) (added on Linux
5.4). If kernel does not support the waitid, pidfd return ENOSYS.
It avoids the need to racy workarounds, such as reading the procfs
fdinfo to get the pid to use along with other wait interfaces.
These interfaces are similar to the posix_spawn and posix_spawnp, with
the only difference being it returns a process file descriptor (int)
instead of a process ID (pid_t). Their prototypes are:
int pidfd_spawn (int *restrict pidfd,
const char *restrict file,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict],
char *const envp[restrict])
int pidfd_spawnp (int *restrict pidfd,
const char *restrict path,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict_arr],
char *const envp[restrict_arr]);
A new symbol is used instead of a posix_spawn extension to avoid
possible issues with language bindings that might track the return
argument lifetime. Although on Linux pid_t and int are interchangeable,
POSIX only states that pid_t should be a signed integer.
Both symbols reuse the posix_spawn posix_spawn_file_actions_t and
posix_spawnattr_t, to void rehash posix_spawn API or add a new one. It
also means that both interfaces support the same attribute and file
actions, and a new flag or file action on posix_spawn is also added
automatically for pidfd_spawn.
Also, using posix_spawn plumbing allows the reusing of most of the
current testing with some changes:
- waitid is used instead of waitpid since it is a more generic
interface.
- tst-posix_spawn-setsid.c is adapted to take into consideration that
the caller can check for session id directly. The test now spawns
itself and writes the session id as a file instead.
- tst-spawn3.c need to know where pidfd_spawn is used so it keeps an
extra file description unused.
Checked on x86_64-linux-gnu on Linux 4.15 (no CLONE_PIDFD or waitid
support), Linux 5.4 (full support), and Linux 6.2.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
2023-08-25 00:42:18 +08:00
|
|
|
#include <sys/wait.h>
|
2023-01-12 21:58:51 +08:00
|
|
|
#include <unistd.h>
|
posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349)
Returning a pidfd allows a process to keep a race-free handle for a
child process, otherwise, the caller will need to either use pidfd_open
(which still might be subject to TOCTOU) or keep the old racy interface
base on pid_t.
To correct use pifd_spawn, the kernel must support not only returning
the pidfd with clone/clone3 but also waitid (P_PIDFD) (added on Linux
5.4). If kernel does not support the waitid, pidfd return ENOSYS.
It avoids the need to racy workarounds, such as reading the procfs
fdinfo to get the pid to use along with other wait interfaces.
These interfaces are similar to the posix_spawn and posix_spawnp, with
the only difference being it returns a process file descriptor (int)
instead of a process ID (pid_t). Their prototypes are:
int pidfd_spawn (int *restrict pidfd,
const char *restrict file,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict],
char *const envp[restrict])
int pidfd_spawnp (int *restrict pidfd,
const char *restrict path,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict_arr],
char *const envp[restrict_arr]);
A new symbol is used instead of a posix_spawn extension to avoid
possible issues with language bindings that might track the return
argument lifetime. Although on Linux pid_t and int are interchangeable,
POSIX only states that pid_t should be a signed integer.
Both symbols reuse the posix_spawn posix_spawn_file_actions_t and
posix_spawnattr_t, to void rehash posix_spawn API or add a new one. It
also means that both interfaces support the same attribute and file
actions, and a new flag or file action on posix_spawn is also added
automatically for pidfd_spawn.
Also, using posix_spawn plumbing allows the reusing of most of the
current testing with some changes:
- waitid is used instead of waitpid since it is a more generic
interface.
- tst-posix_spawn-setsid.c is adapted to take into consideration that
the caller can check for session id directly. The test now spawns
itself and writes the session id as a file instead.
- tst-spawn3.c need to know where pidfd_spawn is used so it keeps an
extra file description unused.
Checked on x86_64-linux-gnu on Linux 4.15 (no CLONE_PIDFD or waitid
support), Linux 5.4 (full support), and Linux 6.2.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
2023-08-25 00:42:18 +08:00
|
|
|
#include <tst-spawn.h>
|
2023-01-12 21:58:51 +08:00
|
|
|
|
|
|
|
/* Nonzero if the program gets called via `exec'. */
|
|
|
|
#define CMDLINE_OPTIONS \
|
|
|
|
{ "restart", no_argument, &restart, 1 },
|
|
|
|
static int restart;
|
|
|
|
|
|
|
|
/* Hold the four initial argument used to respawn the process, plus the extra
|
|
|
|
'--direct', '--restart', the check type ('SIG_IGN' or 'SIG_DFL'), and a
|
|
|
|
final NULL. */
|
|
|
|
static char *spargs[8];
|
|
|
|
static int check_type_argc;
|
|
|
|
|
|
|
|
/* Called on process re-execution. */
|
|
|
|
_Noreturn static void
|
|
|
|
handle_restart (int argc, char *argv[])
|
|
|
|
{
|
|
|
|
assert (argc == 1);
|
|
|
|
|
|
|
|
if (strcmp (argv[0], "SIG_DFL") == 0)
|
|
|
|
{
|
|
|
|
for (int i = 1; i < NSIG; i++)
|
|
|
|
{
|
|
|
|
struct sigaction sa;
|
|
|
|
int r = sigaction (i, NULL, &sa);
|
|
|
|
/* Skip internal signals (such as SIGCANCEL). */
|
|
|
|
if (r == -1)
|
|
|
|
continue;
|
|
|
|
TEST_VERIFY_EXIT (sa.sa_handler == SIG_DFL);
|
|
|
|
}
|
|
|
|
exit (EXIT_SUCCESS);
|
|
|
|
}
|
|
|
|
else if (strcmp (argv[0], "SIG_IGN") == 0)
|
|
|
|
{
|
|
|
|
for (int i = 1; i < NSIG; i++)
|
|
|
|
{
|
|
|
|
struct sigaction sa;
|
|
|
|
int r = sigaction (i, NULL, &sa);
|
|
|
|
/* Skip internal signals (such as SIGCANCEL). */
|
|
|
|
if (r == -1)
|
|
|
|
continue;
|
|
|
|
if (i == SIGUSR1 || i == SIGUSR2)
|
|
|
|
TEST_VERIFY_EXIT (sa.sa_handler == SIG_IGN);
|
|
|
|
else
|
|
|
|
TEST_VERIFY_EXIT (sa.sa_handler == SIG_DFL);
|
|
|
|
}
|
|
|
|
exit (EXIT_SUCCESS);
|
|
|
|
}
|
|
|
|
|
|
|
|
exit (EXIT_FAILURE);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
spawn_signal_test (const char *type, const posix_spawnattr_t *attr)
|
|
|
|
{
|
|
|
|
spargs[check_type_argc] = (char*) type;
|
|
|
|
|
posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349)
Returning a pidfd allows a process to keep a race-free handle for a
child process, otherwise, the caller will need to either use pidfd_open
(which still might be subject to TOCTOU) or keep the old racy interface
base on pid_t.
To correct use pifd_spawn, the kernel must support not only returning
the pidfd with clone/clone3 but also waitid (P_PIDFD) (added on Linux
5.4). If kernel does not support the waitid, pidfd return ENOSYS.
It avoids the need to racy workarounds, such as reading the procfs
fdinfo to get the pid to use along with other wait interfaces.
These interfaces are similar to the posix_spawn and posix_spawnp, with
the only difference being it returns a process file descriptor (int)
instead of a process ID (pid_t). Their prototypes are:
int pidfd_spawn (int *restrict pidfd,
const char *restrict file,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict],
char *const envp[restrict])
int pidfd_spawnp (int *restrict pidfd,
const char *restrict path,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict_arr],
char *const envp[restrict_arr]);
A new symbol is used instead of a posix_spawn extension to avoid
possible issues with language bindings that might track the return
argument lifetime. Although on Linux pid_t and int are interchangeable,
POSIX only states that pid_t should be a signed integer.
Both symbols reuse the posix_spawn posix_spawn_file_actions_t and
posix_spawnattr_t, to void rehash posix_spawn API or add a new one. It
also means that both interfaces support the same attribute and file
actions, and a new flag or file action on posix_spawn is also added
automatically for pidfd_spawn.
Also, using posix_spawn plumbing allows the reusing of most of the
current testing with some changes:
- waitid is used instead of waitpid since it is a more generic
interface.
- tst-posix_spawn-setsid.c is adapted to take into consideration that
the caller can check for session id directly. The test now spawns
itself and writes the session id as a file instead.
- tst-spawn3.c need to know where pidfd_spawn is used so it keeps an
extra file description unused.
Checked on x86_64-linux-gnu on Linux 4.15 (no CLONE_PIDFD or waitid
support), Linux 5.4 (full support), and Linux 6.2.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
2023-08-25 00:42:18 +08:00
|
|
|
PID_T_TYPE pid;
|
|
|
|
siginfo_t sinfo;
|
2023-01-12 21:58:51 +08:00
|
|
|
|
2023-11-15 21:28:34 +08:00
|
|
|
TEST_COMPARE (POSIX_SPAWN (&pid, spargs[0], NULL, attr, spargs, environ), 0);
|
posix: Add pidfd_spawn and pidfd_spawnp (BZ 30349)
Returning a pidfd allows a process to keep a race-free handle for a
child process, otherwise, the caller will need to either use pidfd_open
(which still might be subject to TOCTOU) or keep the old racy interface
base on pid_t.
To correct use pifd_spawn, the kernel must support not only returning
the pidfd with clone/clone3 but also waitid (P_PIDFD) (added on Linux
5.4). If kernel does not support the waitid, pidfd return ENOSYS.
It avoids the need to racy workarounds, such as reading the procfs
fdinfo to get the pid to use along with other wait interfaces.
These interfaces are similar to the posix_spawn and posix_spawnp, with
the only difference being it returns a process file descriptor (int)
instead of a process ID (pid_t). Their prototypes are:
int pidfd_spawn (int *restrict pidfd,
const char *restrict file,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict],
char *const envp[restrict])
int pidfd_spawnp (int *restrict pidfd,
const char *restrict path,
const posix_spawn_file_actions_t *restrict facts,
const posix_spawnattr_t *restrict attrp,
char *const argv[restrict_arr],
char *const envp[restrict_arr]);
A new symbol is used instead of a posix_spawn extension to avoid
possible issues with language bindings that might track the return
argument lifetime. Although on Linux pid_t and int are interchangeable,
POSIX only states that pid_t should be a signed integer.
Both symbols reuse the posix_spawn posix_spawn_file_actions_t and
posix_spawnattr_t, to void rehash posix_spawn API or add a new one. It
also means that both interfaces support the same attribute and file
actions, and a new flag or file action on posix_spawn is also added
automatically for pidfd_spawn.
Also, using posix_spawn plumbing allows the reusing of most of the
current testing with some changes:
- waitid is used instead of waitpid since it is a more generic
interface.
- tst-posix_spawn-setsid.c is adapted to take into consideration that
the caller can check for session id directly. The test now spawns
itself and writes the session id as a file instead.
- tst-spawn3.c need to know where pidfd_spawn is used so it keeps an
extra file description unused.
Checked on x86_64-linux-gnu on Linux 4.15 (no CLONE_PIDFD or waitid
support), Linux 5.4 (full support), and Linux 6.2.
Reviewed-by: Florian Weimer <fweimer@redhat.com>
2023-08-25 00:42:18 +08:00
|
|
|
TEST_COMPARE (WAITID (P_ALL, 0, &sinfo, WEXITED), 0);
|
|
|
|
TEST_COMPARE (sinfo.si_code, CLD_EXITED);
|
|
|
|
TEST_COMPARE (sinfo.si_status, 0);
|
2023-01-12 21:58:51 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
2023-02-14 01:23:19 +08:00
|
|
|
dummy_sa_handler (int signal)
|
2023-01-12 21:58:51 +08:00
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
do_test_signals (void)
|
|
|
|
{
|
2023-03-08 00:31:52 +08:00
|
|
|
/* Ensure the initial signal disposition, ignore EINVAL for internal
|
|
|
|
signal such as SIGCANCEL. */
|
|
|
|
for (int sig = 1; sig < _NSIG; ++sig)
|
|
|
|
sigaction (sig, &(struct sigaction) { .sa_handler = SIG_DFL,
|
|
|
|
.sa_flags = 0 }, NULL);
|
|
|
|
|
2023-01-12 21:58:51 +08:00
|
|
|
{
|
|
|
|
/* Check if all signals handler are set to SIG_DFL on spawned process. */
|
|
|
|
spawn_signal_test ("SIG_DFL", NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
{
|
|
|
|
/* Same as before, but set SIGUSR1 and SIGUSR2 to a handler different than
|
|
|
|
SIG_IGN or SIG_DFL. */
|
|
|
|
struct sigaction sa = { 0 };
|
|
|
|
sa.sa_handler = dummy_sa_handler;
|
|
|
|
xsigaction (SIGUSR1, &sa, NULL);
|
|
|
|
xsigaction (SIGUSR2, &sa, NULL);
|
|
|
|
spawn_signal_test ("SIG_DFL", NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
{
|
|
|
|
/* Check if SIG_IGN is keep as is. */
|
|
|
|
struct sigaction sa = { 0 };
|
|
|
|
sa.sa_handler = SIG_IGN;
|
|
|
|
xsigaction (SIGUSR1, &sa, NULL);
|
|
|
|
xsigaction (SIGUSR2, &sa, NULL);
|
|
|
|
spawn_signal_test ("SIG_IGN", NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
{
|
|
|
|
/* Check if SIG_IGN handlers are set to SIG_DFL. */
|
|
|
|
posix_spawnattr_t attr;
|
|
|
|
posix_spawnattr_init (&attr);
|
|
|
|
sigset_t mask;
|
|
|
|
sigemptyset (&mask);
|
|
|
|
sigaddset (&mask, SIGUSR1);
|
|
|
|
sigaddset (&mask, SIGUSR2);
|
|
|
|
posix_spawnattr_setsigdefault (&attr, &mask);
|
|
|
|
posix_spawnattr_setflags (&attr, POSIX_SPAWN_SETSIGDEF);
|
|
|
|
spawn_signal_test ("SIG_DFL", &attr);
|
|
|
|
posix_spawnattr_destroy (&attr);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
do_test (int argc, char *argv[])
|
|
|
|
{
|
|
|
|
/* We must have either:
|
|
|
|
|
|
|
|
- one or four parameters if called initially:
|
|
|
|
+ argv[1]: path for ld.so optional
|
|
|
|
+ argv[2]: "--library-path" optional
|
|
|
|
+ argv[3]: the library path optional
|
|
|
|
+ argv[4]: the application name
|
|
|
|
|
|
|
|
- six parameters left if called through re-execution:
|
|
|
|
+ argv[1]: the application name
|
|
|
|
+ argv[2]: check SIG_IGN/SIG_DFL.
|
|
|
|
|
|
|
|
* When built with --enable-hardcoded-path-in-tests or issued without
|
|
|
|
using the loader directly. */
|
|
|
|
|
|
|
|
if (restart)
|
|
|
|
handle_restart (argc - 1, &argv[1]);
|
|
|
|
|
|
|
|
TEST_VERIFY_EXIT (argc == 2 || argc == 5);
|
|
|
|
|
|
|
|
int i;
|
|
|
|
for (i = 0; i < argc - 1; i++)
|
|
|
|
spargs[i] = argv[i + 1];
|
|
|
|
spargs[i++] = (char *) "--direct";
|
|
|
|
spargs[i++] = (char *) "--restart";
|
|
|
|
check_type_argc = i++;
|
|
|
|
spargs[i] = NULL;
|
|
|
|
|
|
|
|
|
|
|
|
do_test_signals ();
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
#define TEST_FUNCTION_ARGV do_test
|
|
|
|
#include <support/test-driver.c>
|