From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Add UNSUPPORTED check in elf/tst-pldd.
Date: Wed, 18 Sep 2019 12:45:19 +0200 [thread overview]
Message-ID: <c2ac654e-2bcd-162f-24cb-009e1f97a15a@linux.ibm.com> (raw)
In-Reply-To: <b54014f9-836e-4b14-d206-31e76ee39210@linux.ibm.com>
On 9/17/19 5:17 PM, Stefan Liebler wrote:
> On 9/17/19 3:31 PM, Adhemerval Zanella wrote:
>>
>>
>> On 02/09/2019 12:28, Stefan Liebler wrote:
>>> On 8/29/19 10:47 AM, Florian Weimer wrote:
>>>> * Stefan Liebler:
>>>>
>>>>> On 8/28/19 11:24 AM, Florian Weimer wrote:
>>>>>> * Stefan Liebler:
>>>>>>
>>>>>>> static void
>>>>>>> target_process (void *arg)
>>>>>>> {
>>>>>>> + if (ptrace_scope == 1)
>>>>>>> + {
>>>>>>> + /* YAMA is configured to "restricted ptrace".
>>>>>>> + Disable the restriction for this subprocess. */
>>>>>>> + support_ptrace_process_set_ptracer_any ();
>>>>>>> + }
>>>>>>> +
>>>>>>> pause ();
>>>>>>> }
>>>>>>
>>>>>> I think this has a race condition if pldd attaches to the process
>>>>>> before
>>>>>> the support_ptrace_process_set_ptracer_any call. I have no idea how
>>>>>> hard it is in practice to hit this race. It should be possible to
>>>>>> use a
>>>>>> process-shared barrier or some other form of synchronization to avoid
>>>>>> this issue.
>>>>>>
>>>>>> Thanks,
>>>>>> Florian
>>>>>>
>>>>>
>>>>> I've added a synchronization with stdatomic.h on a shared memory
>>>>> mapping.
>>>>> I've not used pthread* functions as I don't want to link against
>>>>> libpthread.so. Then further adjustments are needed.
>>>>>
>>>>> Or should I just restrict the test ptrace_scope 0 as Adhemerval has
>>>>> proposed in his post?
>>>>
>>>> Is it possible to create a process tree like this?
>>>>
>>>>
>>>> parent (performs output checks)
>>>> subprocess 1 (becomes pldd via execve)
>>>> subprocess 2
>>>>
>>>> If you execve pldd from subprocess 1, wouldn't subprocess 2 in its
>>>> ptrace scope for ptrace_scope < 2?
>>> Yes, this is possible.
>>> I've rearranged the subprocesses. See attached patch.
>>> Now we have a new function pldd_process which forks target_process,
>>> stores the pid of target_prcess to a shared memory mapping as do_test
>>> needs to know this pid.
>>>
>>> Afterwards it execve to pldd which successfully ptrace target_process
>>> in case of "restricted ptrace".
>>>
>>> Please review the usage of support-subprocess-functions.
>>>
>>> Bye,
>>> Stefan
>>>>
>>>> Thanks,
>>>> Florian
>>>>
>>>
>>>
>>> 20190902_tst-pldd.patch
>>>
>>> commit ad51263d51d12ce6ca2ce9304efe5ba05b3912b1
>>> Author: Stefan Liebler <stli@linux.ibm.com>
>>> Date: Mon Aug 26 15:45:07 2019 +0200
>>>
>>> Add UNSUPPORTED check in elf/tst-pldd.
>>> The testcase forks a child process and runs pldd with PID of
>>> this child. On systems where /proc/sys/kernel/yama/ptrace_scope
>>> differs from zero, pldd will fail with
>>> /usr/bin/pldd: cannot attach to process 3: Operation not permitted
>>> This patch checks if ptrace_scope exists, is zero "classic
>>> ptrace permissions"
>>> or one "restricted ptrace". If ptrace_scope exists and has a
>>> higher
>>> restriction, then the test is marked as UNSUPPORTED.
>>> The case "restricted ptrace" is handled by rearranging the
>>> processes involved
>>> during the test. Now we have the following process tree:
>>> -parent: do_test (performs output checks)
>>> --subprocess 1: pldd_process (becomes pldd via execve)
>>> ---subprocess 2: target_process (ptraced via pldd)
>>> ChangeLog:
>>> * elf/tst-pldd.c (do_test): Add UNSUPPORTED check.
>>> Rearrange subprocesses.
>>> (pldd_process): New function.
>>> * support/Makefile (libsupport-routines): Add
>>> support_ptrace.
>>> * support/ptrace.h: New file.
>>> * support/support_ptrace.c: Likewise.
>>
>> LGTM with just a change below, thanks.
>>
>> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>>
> ...
>>> diff --git a/support/ptrace.h b/support/ptrace.h
>>> new file mode 100644
>>> index 0000000000..90006a6b75
>>> --- /dev/null
>>> +++ b/support/ptrace.h
>>> @@ -0,0 +1,32 @@
>>> +/* Support functions handling ptrace_scope.
>>> + Copyright (C) 2019 Free Software Foundation, Inc.
>>> + 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/>. */
>>> +
>>> +#ifndef SUPPORT_PTRACE_H
>>> +#define SUPPORT_PTRACE_H
>>> +
>>> +#include <sys/cdefs.h>
>>> +
>>> +__BEGIN_DECLS
>>> +
>>> +/* Return the current YAMA mode set on the machine (0 to 3) or -1
>>> + if YAMA is not supported. */
>>> +int support_ptrace_scope (void);
>>> +
>>> +__END_DECLS
>>> +
>>> +#endif
>>
>> I think it should named xptrace.h.
>>
> ...
> Okay. Then I will rename it to support/xptrace.h and if nobody opposes,
> I'll commit it tomorrow.
>
> Thanks for the review.
> Stefan
>
Committed with xptrace.h instead of ptrace.h.
next prev parent reply other threads:[~2019-09-18 10:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 10:19 [PATCH] Add UNSUPPORTED check in elf/tst-pldd Stefan Liebler
2019-08-27 15:06 ` Adhemerval Zanella
2019-08-27 15:14 ` Florian Weimer
2019-08-27 19:11 ` Adhemerval Zanella
2019-08-28 9:06 ` Stefan Liebler
2019-08-28 9:24 ` Florian Weimer
2019-08-28 14:42 ` Stefan Liebler
2019-08-29 8:47 ` Florian Weimer
2019-09-02 15:28 ` Stefan Liebler
2019-09-17 13:31 ` Adhemerval Zanella
2019-09-17 15:17 ` Stefan Liebler
2019-09-18 10:45 ` Stefan Liebler [this message]
2019-09-18 15:17 ` Joseph Myers
2019-09-19 10:28 ` Stefan Liebler
2019-09-02 19:37 ` Adhemerval Zanella
2019-09-03 6:30 ` Stefan Liebler
2019-09-03 13:34 ` Adhemerval Zanella
2019-09-06 3:21 ` Carlos O'Donell
2019-09-10 8:46 ` Stefan Liebler
2019-09-10 13:32 ` Adhemerval Zanella
2019-09-11 7:05 ` Stefan Liebler
2019-08-28 12:19 ` Adhemerval Zanella
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2ac654e-2bcd-162f-24cb-009e1f97a15a@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=libc-alpha@sourceware.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).