public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Anatol Pomozov <anatol.pomozov@gmail.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: 0.161 elfutils test are failing on Linux Arch
Date: Fri, 16 Jan 2015 06:12:21 -0800	[thread overview]
Message-ID: <CAOMFOmUbyApy5pPf660d=4rSWsqx2Nja5kFiLZN=S6cJ7wBYQw@mail.gmail.com> (raw)
In-Reply-To: 1421320011.26117.11.camel@bordewijk.wildebeest.org

[-- Attachment #1: Type: text/plain, Size: 2853 bytes --]

Hi

On Thu, Jan 15, 2015 at 3:06 AM, Mark Wielaard <mjw@redhat.com> wrote:

> Hi Anatol,
>
> On Wed, 2015-01-14 at 13:30 -0800, Anatol Pomozov wrote:
> > On Wed, Jan 14, 2015 at 1:16 PM, Mark Wielaard <mjw@redhat.com> wrote:
> > > You do seem to have yama and alternate selinux security module enabled
> > > it seems. Make sure it doesn't deny ptrace/proc/mem.
> > > Probably /proc/sys/kernel/yama/ptrace_scope should be set to zero.
> > >
> > Thanks for your pointer. My computer has YAMA indeed. The default
> > ptrace_scope value is YAMA_SCOPE_RELATIONAL (1) and it is what my
> computer
> > has.
> >
> > I temporary disabled YAMA with
> > # sudo sysctl kernel.yama.ptrace_scope=0
> >
> > and now tests are passed:
> >
> >
> ============================================================================
> > Testsuite summary for elfutils 0.161
> >
> ============================================================================
> > # TOTAL: 129
> > # PASS:  127
> > # SKIP:  2
> > # XFAIL: 0
> > # FAIL:  0
> > # XPASS: 0
> > # ERROR: 0
>
> Awesome! BTW. Which architecture and what are the two SKIPPED tests?
>

I have x86_64 and the skipped tests are

SKIP: run-backtrace-native-core.sh
SKIP: run-backtrace-native-core-biarch.sh


> So what I (as a packager) suppose to do here? I doubt that YAMA will be
> > disabled in the default kernel. Should I just ignore these test failures?
> > Or maybe "make check" should ignore these 2 tests if YAMA enabled?
>
> Lets see if we can change the tests first to allow proper introspection
> in this case (which hopefully also helps in the selinux case). I think
> for the vdsosyms test we can just fork a child process instead to look
> at the vdso instead of picking a random process. Currently it does:
>   /* Take our parent as "arbitrary" process to inspect.  */
>   pid_t pid = getppid();
> And for the deleted test we can probably first call
> prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, 0, 0, 0) to allow eu-stack -p
> to get at the memory image of the deleted-lib.so.
>
> I'll try to code something up and if you could test that, that would be
> awesome.
>

Thanks. The patch works great. All tests are passed now.


>
> But... This is really workarounds for the testcases. Then we know the
> functionality works as intended. Except when a real user uses the dwfl
> attach library calls or eu-stack binary...
>
> So we probably need to figure out how to really fix this. How do other
> tools and libraries work? What if a user wants to see why firefox is
> wonky and does a strace -p $(pidof firefox) or gstack $(pidof firefox).
> Are those tools also broken by default on Arch? Or do they use some
> other trick to work properly?
>

I get "Operation not permitted", my understanding that in this case user
should use sudo.

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3991 bytes --]

             reply	other threads:[~2015-01-16 14:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 14:12 Anatol Pomozov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-20 14:30 Mark Wielaard
2015-01-17 14:04 Dmitry V. Levin
2015-01-16 17:21 Josh Stone
2015-01-16 16:02 Mark Wielaard
2015-01-15 12:56 Mark Wielaard
2015-01-15 11:06 Mark Wielaard
2015-01-14 21:30 Anatol Pomozov
2015-01-14 21:16 Mark Wielaard
2015-01-14 19:51 Anatol Pomozov
2015-01-14 19:41 Mark Wielaard
2015-01-14 19:19 Anatol Pomozov

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='CAOMFOmUbyApy5pPf660d=4rSWsqx2Nja5kFiLZN=S6cJ7wBYQw@mail.gmail.com' \
    --to=anatol.pomozov@gmail.com \
    --cc=elfutils-devel@lists.fedorahosted.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).