linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: linuxppc-dev@ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: ADDR_COMPAT_LAYOUT breaks PTRACE_SEIZE
Date: Sun, 22 Mar 2015 16:39:44 +0100	[thread overview]
Message-ID: <87pp81nirj.fsf@igel.home> (raw)

On ppc64, a process running with the ADDR_COMPAT_LAYOUT personality
causes ptrace(PTRACE_SEIZE) to hang in the kernel, unkillable.

#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <sys/personality.h>
#include <sys/ptrace.h>
#include <sys/wait.h>

int
main (void)
{
  pid_t child;

  personality (ADDR_COMPAT_LAYOUT);
  child = fork ();
  if (child == 0)
    {
      kill (getpid (), SIGSTOP);
      exit (0);
    }

  ptrace (PTRACE_SEIZE, child, NULL, NULL);
  wait (NULL);
  ptrace (PTRACE_CONT, child, NULL, NULL);
}

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

                 reply	other threads:[~2015-03-22 15:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87pp81nirj.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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 NNTP newsgroup(s).