public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>, freswa@archlinux.org
Subject: Re: [PATCH] Linux: Terminate subprocess on late failure in tst-pidfd (bug 29485)
Date: Mon, 15 Aug 2022 10:23:10 -0400	[thread overview]
Message-ID: <788eb46d-cfe9-cdcf-86fe-a3e366193eff@redhat.com> (raw)
In-Reply-To: <87tu6ejcbe.fsf@oldenburg.str.redhat.com>

On 8/15/22 01:38, Florian Weimer via Libc-alpha wrote:
> ---
>  sysdeps/unix/sysv/linux/tst-pidfd.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/sysdeps/unix/sysv/linux/tst-pidfd.c b/sysdeps/unix/sysv/linux/tst-pidfd.c
> index 037af22290..5711d1c312 100644
> --- a/sysdeps/unix/sysv/linux/tst-pidfd.c
> +++ b/sysdeps/unix/sysv/linux/tst-pidfd.c
> @@ -147,8 +147,11 @@ do_test (void)
>         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_COMPARE (pidfd_send_signal (pidfd, SIGKILL, NULL, 0), 0);
> +	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);
> 
I reviewed the original and missed this. Thanks.

On line 107 we fork the new process.

On line 150 we are testing for the unsupported failure but the child process is still alive.

You add the termination via TEST_COMPARE sending SIGKILL via pidfd_send_signal.

LGTM.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

-- 
Cheers,
Carlos.


      reply	other threads:[~2022-08-15 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  5:38 Florian Weimer
2022-08-15 14:23 ` Carlos O'Donell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=788eb46d-cfe9-cdcf-86fe-a3e366193eff@redhat.com \
    --to=carlos@redhat.com \
    --cc=freswa@archlinux.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).