mirror of
git://sourceware.org/git/glibc.git
synced 2024-11-27 03:41:23 +08:00
tst-pidfd.c: UNSUPPORTED if we get EPERM on valid pidfd_getfd call
pidfd_getfd can fail for a valid pidfd with errno EPERM for various reasons in a restricted environment. Use FAIL_UNSUPPORTED in that case. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
This commit is contained in:
parent
35363b53ce
commit
325ba824b0
@ -142,6 +142,13 @@ do_test (void)
|
||||
xrecvfrom (sockets[0], &remote_fd, sizeof (remote_fd), 0, NULL, 0);
|
||||
|
||||
int fd = pidfd_getfd (pidfd, remote_fd, 0);
|
||||
/* pidfd_getfd may fail with EPERM if the process does not have
|
||||
PTRACE_MODE_ATTACH_REALCREDS permissions. This means the call
|
||||
may be denied if the process doesn't have CAP_SYS_PTRACE or
|
||||
if a LSM security_ptrace_access_check denies access. */
|
||||
if (fd == -1 && errno == EPERM)
|
||||
FAIL_UNSUPPORTED ("don't have permission to use pidfd_getfd on pidfd, "
|
||||
"skipping test");
|
||||
TEST_VERIFY (fd > 0);
|
||||
|
||||
char *path = xasprintf ("/proc/%d/fd/%d", pid, remote_fd);
|
||||
|
Loading…
Reference in New Issue
Block a user